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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Refreshing Embedded Objects

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Refreshing Embedded Objects

    Hi All,

    I have a bunch of embedded UXs that are placed inside a main panel for a mobile app. Inside these embedded UXs are controls with client-side show/hide conditions, which is the value of a text box in the parent component. When this value is placed inside the textbox, however, the controls do not appear like they should. I've tried using .refreshClientSideComputations() on the dialog, both on the parent and on the child components, as well as outputting the values of the textbox to make sure its read properly. The child component is accessing the variable correctly, I just can't wrap my head around why this isn't working.

    Anyone have any ideas or something small I may have overlooked?

    Thanks!
    Tags: None
    #2
    Re: Refreshing Embedded Objects

    If you have delay render checked it SHOULD reload when brought into view with the new values. If you have restore from variables or the cache in a list control it might cause an issue in that way but other than that it should work as expected. Remember that the "client-side" has nothing to do with setting the value of an argument when the component loads as a child component - so keep in mind that the server is getting the value of the argument - then loading the embedded component, which is why if it reloads when it is brought into view via delay render in the panel card setting it loads as expected.
    You could - load all of the embedded components and put them in containers that you show/hide because the containers are outside of the embedded process and loaded with the initial UX therefore available for to the client-side show/hide stuff which might be what you're looking for.
    Try putting the embedded stuff in a container and show/hide THAT
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment

      #3
      Re: Refreshing Embedded Objects

      Originally posted by CharlesParker View Post
      You could - load all of the embedded components and put them in containers that you show/hide because the containers are outside of the embedded process and loaded with the initial UX therefore available for to the client-side show/hide stuff which might be what you're looking for.
      Try putting the embedded stuff in a container and show/hide THAT
      I did that inside the embedded process already, i.e., the controls that are client side hidden are inside containers INSIDE the embedded process, because the embedded UXs are in panels on the main UX. Is there any other way to work around this?

      Thanks!

      Comment

        #4
        Re: Refreshing Embedded Objects

        OK, so from your answer I think you understand that the show hide is going on inside the component regardless of what is show/hide.
        I think the next step is to set the changing value to an argument instead of a yes/no THEN set the argument at the parent level so when the embedded component loads - it gets the values as arguments and passes them to the embedded component when it renders.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

          #5
          Re: Refreshing Embedded Objects

          Originally posted by jjedrasik View Post
          Hi All,

          I have a bunch of embedded UXs that are placed inside a main panel for a mobile app. Inside these embedded UXs are controls with client-side show/hide conditions, which is the value of a text box in the parent component. When this value is placed inside the textbox, however, the controls do not appear like they should. I've tried using .refreshClientSideComputations() on the dialog, both on the parent and on the child components, as well as outputting the values of the textbox to make sure its read properly. The child component is accessing the variable correctly, I just can't wrap my head around why this isn't working.

          Anyone have any ideas or something small I may have overlooked?

          Thanks!
          Can you post an example of one of your client-side show/hide expressions that is not working?

          Comment

            #6
            Re: Refreshing Embedded Objects

            Hi all,

            Thanks everyone for the help, I managed to solve it by using .getChildObject, and setting a 1/0 in the embedded component. Thus there is now a control in the child component that controls the show/hide, as opposed to the parent.

            Thanks again!

            Comment

              #7
              Re: Refreshing Embedded Objects

              Glad you resolved it, not sure if I ever fully understood your issue or if I helped in any way. One thing about posting a question and discussing it is that you often find yourself digging into your own issue in a more thought provoking way, sometimes adding in a control or a slightly different approach and then a light comes on...
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment

                #8
                Re: Refreshing Embedded Objects

                Jan's issue was that he based his Embedded UX Component client-side simple show/hide expression on a parent control. The child UX has no idea what's going on in the parent.

                Embedded components are... more or less... separate from their parent. Upon render, the embedded component should get a pointer to the parent get the parent control value and set a child control value that the show/hide will be based on. Firing off this process from the parent is tricky because your child ux may not be there yet.

                You can base the expression on a parent control by using a Javascript function to control the show/hide. The function would get a pointer to the parent, get the control value, and the function would return the appropriate value for the expression. I would think this is preferable to keeping 2 (or more) parent and child controls updated.

                Comment

                  #9
                  Re: Refreshing Embedded Objects

                  Originally posted by Davidk View Post
                  Jan's issue was that he based his Embedded UX Component client-side simple show/hide expression on a parent control. The child UX has no idea what's going on in the parent.

                  Embedded components are... more or less... separate from their parent. Upon render, the embedded component should get a pointer to the parent get the parent control value and set a child control value that the show/hide will be based on. Firing off this process from the parent is tricky because your child ux may not be there yet.

                  You can base the expression on a parent control by using a Javascript function to control the show/hide. The function would get a pointer to the parent, get the control value, and the function would return the appropriate value for the expression. I would think this is preferable to keeping 2 (or more) parent and child controls updated.
                  This sums up the issue exactly. Thanks for the clarification on the relationship between parent/child UXs.

                  Comment

                  Previous template Next
                  Working...
                  X