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 arguments PARENT UX to CHILD UX

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

    Passing arguments PARENT UX to CHILD UX

    I have a fairly complex UX that is having trouble passing content
    to an embedded UX.

    For diagnosis, I've created a couple of basic PARENT UX components
    and one CHILD UX. These are included as an attachment in ZIP format
    and with A5W files to launch them.


    Passing a textbox value DIRECTLY (00_test_arg_pass_10_Parent_PANEL-TB)
    • When a TEXTBOX has a default value and is passed through the argument the parameter is passed successfully.
    • However, if the textbox value is changed, the argument is NOT passed to the embedded (child) UX on second or subsequent activations.



    Passing a textbox value BY JAVASCRIPT (00_test_arg_pass_10_Parent_PANEL-JS)
    • Where the argument is passed, a small javascript function is used to pick up the value from a textbox. The function fires (alerts are launched). However, the value does NOT pass to the child. Oddly, the command to call the javascript function is in fact passed to the CHILD.
    • As in the prior example, second or subsequent activations do not appear to call the function again.



    As an aside, I have other cases where the "onPanelActivate" will not fire
    in the CHILD UX even though the documented conditions appear to be met.

    If you have examples of PARENT-to-CHILD argument passing or have input on
    my examples please let me know!



    0_test_argument_passing.zip

    #2
    Re: Passing arguments PARENT UX to CHILD UX

    It's important that you tell us what version of Alpha you're using.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Passing arguments PARENT UX to CHILD UX

      I keep my system up-to-date. The challenge I've had with arguments
      and with the occasions where the "onPanelActivate" simply won't fire (ever)
      has been consistent across versions.

      Alpha Anywhere v12.4.5.4.6
      Build 5206

      Comment


        #4
        Re: Passing arguments PARENT UX to CHILD UX

        I believe your build is the last official release... 5447-5206.

        onPanelActivate is fired under very specific circumstances. It does not fire when the Parent first loads and navigates to the PanelCard of the Child UX. If you navigate away from the Child UX, and then navigate back to the Child UX, onPanelActivate of the Child UX fires.

        You could set a State Variable in the Parent UX. Then you could use the Parent Embedded Object onLoadComplete property to run Javascript to get the Parent's State Variable. But... that doesn't work because even though the Child UX is loaded, you cannot access the Parent UX at this point.

        You can't use an Argument easily, because that value never gets updated... because the Child UX is never re-built and the argument never re-valued.

        I believe you must use 2 Events.

        Create a Javascript function in the Child UX which reaches into the Parent UX and gets either a State Variable you set up, or use .getValue() to get the value of a Parent control.

        Then call that Javascript function from both the Child UX onRenderComplete AND onPanelActivate events.

        Now you have data from the Parent UX. Set the value of a Child UX Textbox, and use that Textbox as the basis for Child UX argument for Lists etc.

        onRenderComplete runs once when the Child UX is first rendered... first accessed.
        onPanelActivate run every time AFTER the Child UX is first rendered.
        Last edited by Davidk; 11-10-2018, 08:30 PM.

        Comment


          #5
          Re: Passing arguments PARENT UX to CHILD UX

          Dave,

          Thanks for the detail.

          I had already built a workaround (reaching back into the parent to grab a variable) but
          my hope had been (oddly) that I was doing something wrong and there was an easier
          or "proper" way to do this.

          Some days, I just shake my head.

          I have one case where despite seeming to meet all the requirements for the "onPanelActivate"
          will simply not fire... ever. The UX is embedded, has a unique alias, and is fairly simple...
          ... seems to be some kind of artifact in the code under the covers.

          Again, thanks for the input.

          Comment


            #6
            Re: Passing arguments PARENT UX to CHILD UX

            Ok... glad you had already solved the issue... good to know.

            Comment


              #7
              Re: Passing arguments PARENT UX to CHILD UX

              Perhaps this does not apply to UX's embedded in other UX's, but another event in the child UX to consider is "onSynchronizeDialog".

              Is Alpha calling this event in your situation?

              I use that event, in addition to "onRenderComplete" to handle cases when alpha "opens" a UX in a popup or tabbedUI that was previously opened. This happens when I allow Alpha to use a "cached" (previously openend) UX, in which case Alpha calls "onSynchronizeDialog" instead of "onRenderComplete".

              Comment

              Working...
              X