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

hideWaitMessage firing too soon

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

    hideWaitMessage firing too soon

    I have a list in a UX that persists data, and I have Javascript that refreshes the list data when the UX is opened. The list has lots of data so it can take a several seconds to refresh.

    Per the javascript, the showWaitMessage fires before the refreshListData, and then a hideWaitMessage is used the onListReady event of the list.

    The hideWaitMessage consistently disappears before the list is totally rendered or refreshed (or something). Users will see the message disappear, click on a record and start interacting with it, and then the list actually finishes refreshing and changes what they've worked on or execute show/hide or enable/disable Javascript that's confusing.

    I've tried putting the hideWaitMessage in several of the list events and haven't had any better success. Is there a better way to tell that the UX and list data are truly finished loading so I can keep the wait message up until it's safe to start working?

    #2
    Re: hideWaitMessage firing too soon

    This is another example of how bad, and wrong, the Alpha documentation is.

    A good tip that works for some methods, and does work for showWaitMessage, is to create Action Javascript... and then turn that action into code. The action has a property for "Auto close after how many milliseconds". Fill that in and when you turn the action into code you'll see how it's used...

    Code:
    {dialog.object}.showWaitMessage('container:CONTAINER_1',{useCSSAnimation: false,message: 'Wait...',icon: 'css/A5System/Images/wait.gif',waitMessageAutoCloseDelay: 10000});
    In the in-line help for this action, in the milliseconds property, you'll see a reference to {dialog.Object}.waitMessageAutoCloseDelay. This is a dialog property you can set in your Javascript code.

    Set a long wait message time and then your hideWaitMessage() will close the message when you run it.

    Code:
    {dialog.Object}.waitMessageAutoCloseDelay = 65000;
    {dialog.object}.showWaitMessage('container:CONTAINER_1',{useCSSAnimation: false,message: 'Wait...',icon: 'css/A5System/Images/wait.gif'});

    Comment


      #3
      Re: hideWaitMessage firing too soon

      Try following the action javascript we have in the image below. It works well for several applications. In this case, we are requesting the user click a button to refesh, but you don't have to do that. Use any event you want to trigger it.sync_process.png

      Make sure to check the box "run actions synchronously" at the bottom.

      Comment


        #4
        Re: hideWaitMessage firing too soon

        It's been a long night, so I'm not going to try the correct terminology.
        JavaScript by default does not wait for one command to finish before executing the next command.
        I believe the solution is to wrap the code to refreshListData in a function.
        This link explains it much better than I do https://www.freecodecamp.org/news/ja...-1cc090ddad99/.
        Gregg
        https://paiza.io is a great site to test and share sql code

        Comment


          #5
          Re: hideWaitMessage firing too soon

          Which List events have you tried? In my UX, refreshing a 35,000 row list take approx. 12-15 seconds. Using onListDraw seems to work well - I put the .hideWaitMessage() in there.

          Comment


            #6
            Re: hideWaitMessage firing too soon

            Your issue is common and that is why Alpha has an action that fires once the sync is complete. You can use that along with what I mentioned. What we have instituted works really well, but it does add a layer of control on top which prevents the user from clicking on the list until it's been refreshed. You could use the server side "after sync" event as well as the "after save confirmation". Both are in the list detail properties. I think there are a lot of built in options it just depends on your specific use case and requirements.

            You could also take full control of the sync process if you want...and handle it all programmatically and remove most of the javascirpt calls. We did that on one project and it was a pain - but it did work. We had to do that for a different reason though.

            Good luck.

            Comment

            Working...
            X