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



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 values between components

  • Filter
  • Time
  • Show
Clear All
new posts

    Passing values between components


    I have an a.5w page with 2 separate UX components. I pass values between them via session variables and trigger the transfer with a button click


    Works fine on desktop browsers but not mobile browsers. Any idea's or alternative methods for doing this?


    Re: Passing values between components

    What do you mean you trigger the transfer?

    What, exactly, is your button doing and where is the button?

    When you modify a session variable, the session variable exists on the server end. So the next time you run an xbasic function, it will use the current session variable value.


      Re: Passing values between components


      UX Component 1: sets a session variable and runs $('_260UXJOBFLOW.V.R1.BUTTON_1').click(); this button is on UX Component 2

      UX Component 2: the xbasic triggered by the click event (above) reads the session variable and I get the functionality I need

      Except not on mobile browsers?


        Re: Passing values between components

        Why does it have to be two UXs?

        Could you just combine them into one UX with 2 panels?

        You look like you are using the direct name of the button - and the button is probably ending up with a different name on a mobile device than it has on a windows device.


          Re: Passing values between components

          Session variables should not be used this way. It is best to only use session variables to keep information that is set at login time and never changed while the user is logged in.


            Re: Passing values between components

            It is best to only use session variables to keep information that is set at login time and never changed while the user is logged in.
            I always treat session variables with great respect... the developer should always know how, and where, they're being used... but I'm not sure I could agree with setting session vars only at login... and then never change them.


              Re: Passing values between components

              Yes you have to be carful but I change the value of session variables regularly without issue and I don't believe its my use of a session variable that's the issue.

              Originally posted by lgrupido View Post
              You look like you are using the direct name of the button - and the button is probably ending up with a different name on a mobile device than it has on a windows device.
              Yes I expect that is the problem and I'm looking for a work around. I wish I could combine the 2 UX components but that's not practical for various reasons.


                Re: Passing values between components

                You could try the following methods:

                PUSH the data from one UX to the other.

                Refresh the entire page. The session variable will still hold it's value, and you can read it in the other component.

                Hard Code the name of the second UX. Then you won't have to worry about it changing names.

                I don't know how to DO all of these, but those methods should work.


                  Re: Passing values between components


                  In the Alpha IDE, go to the "Help" menu and select "Video Finder" and then set the Filter to M43

                  After that video, view D37 and M45.

                  If those videos still don't cover exactly what you need then set the video finder filter to:

                  There are a bunch of videos on the topic of passing data between components. It's just too difficult to give one single answer on passing data around.

                  When passing data between components you have to consider if you need the data to be present at the server while the server is preparing the component, if so then Arguments is a good way to go with UX to UX and from Grid to UX or from TabbedUI to Grid/UX.