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

Understanding onRenderComplete

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

    Understanding onRenderComplete

    Web app running 5667-5254.

    Alpha's description of the client-side event 'onRenderComplete' is: Last event to fire when the UX is rendered.

    Am I correct in assuming then that anything I write in this event is the very last code to run? Doesn't seem to be the case.

    Why is it I need to use a setTimeout() to get my code to run properly? Without a setTimeout() I have to refresh the browser to get this to populate. Which is weird. What's the difference between navigating to an A5W page and refreshing it?

    Ashampoo_Snap_Thursday, June 6, 2019_12h33m55s_008_.png

    Ashampoo_Snap_Thursday, June 6, 2019_12h33m24s_007_.png

    Ashampoo_Snap_Thursday, June 6, 2019_12h34m53s_009_.png

    I don't really care that I need to use a setTimeout(). I just want to better understand what is going on here.

    Thanks.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    #2
    Re: Understanding onRenderComplete

    There's information missing from your post which may help clarify things a bit.
    Is your UX using Integrated Login?

    If so, remember what's going on regarding a Login process. onRenderComplete is the last event to fire (as far as I can see... I didn't test all of them). Your UX is rendered... all done... so how can you have any login information. You haven't logged in yet. Once you log in, you can have your USERNAME... but only after it's ready.

    onRenderComplete may be the wrong place to put your code... although it doesn't make it any better putting it anywhere else.

    The better place to put this code is in the Client-side Event afterLogin. But... you still don't have your USERNAME right away. When you log in, Alpha makes an Ajax Callback to log you in. Only then do you have your USERNAME. So... it looks like a setTimeout is always required. The Argument just isn't ready yet.

    However, the Server-side event onLogin will always have some login information. afterLogin will not.

    I believe afterLogin was really only intended to be used to navigate around a UX after a login.

    In onLogin, you get your login userid, and you get to set e.userNameFriendly. e.userNameFriendly is passed directly to afterLogin.

    So, what you probably want to do, is set your e.userNameFriendly property in onLogin, and then you'll always have e.userNameFriendly in afterLogin... and not have to use a setTimeout.

    Comment


      #3
      Re: Understanding onRenderComplete

      Originally posted by Davidk View Post
      Is your UX using Integrated Login?
      No. This isn't a login component.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Re: Understanding onRenderComplete

        Just to be a bit specific... there is a login component... and there is a UX with Integrated Login.

        Comment


          #5
          Re: Understanding onRenderComplete

          Yes but I don't believe the login process is an issue ...I'll explain...

          Upon successful login my users then hit a dashboard page (all pages/components are individual. I don't use embedded components here or panels for navigation). The dashboard page also has the same code to populate the user's name. I don't have a problem with the dashboard. From the dashboard the user can navigate to a number of other components/pages. These components have the same code as well. Most of the time the user's name populates. Every so often, like by screenshot shows, it doesn't.

          Come to think of it I'm using the same span ID in every component (I have a template I use. Makes development quicker). I wonder if this is a problem even though I have seperate A5W pages.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #6
            Re: Understanding onRenderComplete

            If the spans winds up in the same DOM, then only the first span will get set.

            Comment

            Working...
            X