Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Passing Variables between compoents

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Passing Variables between compoents

    I am using Alpha 12
    I have an action button in the Toolbar of a Grid component.
    The action button opens a UX component.
    I would like to pass a variable from the grid component (value of a field in the component) to the UX component.
    Can someone tell me the best method for doing this.

    #2
    Re: Passing Variables between compoents

    I have answered my own question. I found a great video (M41) in the video library that show exactly how to set a session variable inside a action call-back.

    Comment


      #3
      Re: Passing Variables between compoents

      Hey Richard. I am in the middle of the same thing, but am not having any success. I created session variables from the "set session variables" button within the "open dialog component". I used the samples that they provided and constructed this:

      myVar1 = {javascript}function(rowNum) { return {grid.object}.getValue('G','FIELD_ID',rowNum); }(rowNum)
      myVar2 = "test"

      When I refer to them through a JS alert or check it out in the debug, they are undefined. Do you have any insight? Did you have any problem setting values for the session variables?

      Comment


        #4
        Re: Passing Variables between compoents

        I used the same example and the variable returns a null string. I can't get it to work either.
        I'll let you know if I come up with a solution.

        Comment


          #5
          Re: Passing Variables between compoents

          I find it troublesome to get session variables to work the same between Working Preview mode and W.A.S. So, I uses Arguments or the browser's "window" namespace object to pass information. Have you looked at these videos: M36, M42, M43, M53, D15, 69. Also, another technique I've started to use is the state info object - video M58.

          Comment


            #6
            Re: Passing Variables between compoents

            Thanks for your input, I did watch one of the videos on using windows namespace and will follow up with the others.

            Comment


              #7
              Re: Passing Variables between compoents

              I solved my problem by grabbing the primary key using the request.variables.__PKValue value when onDialogInitialize fires. This hands me the primary key from the selected row of the grid that calls the dialog. I use it to make SQL queries in Xbasic against the DB and then send the JS to the client.

              Another way that worked was to set a cookie using JS from the parent component, then using Xbasic to grab it before it goes to the client. The object is "request.Variables.cookieName". A word of warning, if you want to grab data this way there are url spaces ("%20") that have to be stripped out. There might be a conversion function out there, but I didn't find it, so I did some simple regex to clean it up. Here's a sample:

              if variable_exists("request.Variables.cookieVar")
              CookieValue = request.Variables.cookieVar
              xx = regex_merge(CookieValue,"%20"," ")
              xx = "\"" + xx + "\""
              e.control.ChildFieldName = xx
              end if

              One final way that I figured out and don't like at all, is to let the child page render client side and then immediately do an ajax callback that sends the data back to the server. There you can use e.datasubmitted to work with the data and then send it back when you're done in Xbasic. It's clunky and adds to the initial load time, but then again, most people wouldn't notice it.

              There may be a way to grab the window namespace from the server, but I searched the debug and did not find it. I'm assuming that the info doesn't leave the browser.

              I had no luck with session variables.

              Hope this helps. If someone knows other ways, I'd be excited to hear about it.

              Comment


                #8
                Re: Passing Variables between compoents

                OK, I'll give it a try.

                Comment

                Working...
                X