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

Communication between Components

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

    Communication between Components

    I have a parent UX called Loads

    In the loads UX I have an embedded pagelayout named Stops, alias Stops.

    In the pagelayout there is a UX named Pickup, alias Pickup. It is the only component in the pagelayout.

    I want the parent UX to execute methods on controls in the Pickup UX.

    I have not been able to figure out how to get a pointer to the Pickup UX.

    I have tried var pickup = {dialog.object}.getChildObject('STOPS_PICKUP');

    Any help is appreciated.

    #2
    Re: Communication between Components

    That was a really well structured question... thanks.

    I believe I've put together the same structure that you have.

    This code... the same as yours... seems to work. What methods do you want to use?

    Code:
    debugger;
    var cObj = {dialog.Object}.getChildObject('STOPS_PICKUP');
    var name = cObj.getValue('FIRSTNAME');
    I have a Firstname control on the UX which is a UX Component inside a Page Layout.
    My PageLayout is embedded into a Parent UX

    I have a button on the Parent UX executing the code above. Name is set.

    Comment


      #3
      Re: Communication between Components

      You solved my problem!

      This is what I had been trying to test:

      var pickup = {dialog.object}.getChildObject('STOPS_PICKUP');
      var val = {dialog.object}.getValue('ShipperIndex_PK');
      alert(val);

      This is what works:

      var pickup = {dialog.object}.getChildObject('STOPS_PICKUP');
      var val = pickup.getValue('ShipperIndex_PK');
      alert(val);

      I assumed my pointer was that part that didn't work. I should have posted the whole snippet.

      This is a new technique to me. Now that I know how to do it correctly. I can use any number of methods.

      Hopefully, others can benefit from this example.

      Thanks for your help

      Comment


        #4
        Re: Communication between Components

        Yes... your original code is pointing to the parent object.
        It's interesting that alpha puts the page and embedded object aliases together to id the object... very cool I though.
        Glad you got it working.

        Comment


          #5
          Re: Communication between Components

          Another piece of this puzzle....

          From the Pickup UX, how to use methods of controls in the Loads UX?

          The parent of the Pickup UX is the pageLayout, so the Loads UX is a grandparent.

          How do you pass values to a grandparent?

          Comment


            #6
            Re: Communication between Components

            I'm trying to make this work using getTopParentObject()

            So far, this throws and alert of "false"

            var parentObj = {dialog.object}.getTopParentObject({dialog.object}.getValue('FreightBillNum'));
            alert(parentObj);


            And this gives no alert at all

            var parentObj = {dialog.object}.getTopParentObject();
            var FBnum = parentObj.getValue('FreightBillNum');
            alert(FBnum);


            Again, all help is appreciated.

            Comment


              #7
              Re: Communication between Components

              Just curious. Why involve the PageLayout component?

              You have only 1 UX in the PageLayout... anything else?

              Comment


                #8
                Re: Communication between Components

                The pagelayout will have several components. Pickups and deliveries, up to 10. I am just starting to build it and I want to get the communication script working first.

                Comment


                  #9
                  Re: Communication between Components

                  I think you'd be better off using a UX instead of the PageLayout. Same idea... way more flexibility... far more current.

                  The PageLayout is not a true component the way the Grid and UX are. You can't get a parent object of a PageLayout.

                  You'd have to hard code the object reference which is not a good idea. DLG1_DlgObj would get you the parent in this case... but not advisable.

                  Comment


                    #10
                    Re: Communication between Components

                    You may be right. The pagelayout seems like a good tool because of the built-in ability to show/hide tabs.

                    Comment

                    Working...
                    X