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

Javascript timing issue

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

    Javascript timing issue

    The following code appears to be running too fast. The list doesn't always refresh.
    I can't seem to figure out how one slows down javascript code or if it's even possible.

    Thanks

    Code:
    A5.msgBox.show('Delete Labor Entry','<div style=\' padding: 10pt;\'>Delete This Labor Entry?</div>','yn',function(button) {
    if(button == 'yes'){
    	{dialog.object}.ajaxCallback('','','deleteMechEntry','','',{deviceOfflineFunction: function() {   }});
    	{dialog.object}.panelSetActive('PANELCARD_LIST',true);
    	
    	{dialog.object}.refreshListData('FIXENTRIES');
    	}
    });
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    #2
    Re: Javascript timing issue

    You could experiment with setTimeout: http://www.w3schools.com/jsref/met_win_settimeout.asp

    Code:
    A5.msgBox.show('Delete Labor Entry','<div style=\' padding: 10pt;\'>Delete This Labor Entry?</div>','yn',function(button) {
    if(button == 'yes'){
    	{dialog.object}.ajaxCallback('','','deleteMechEntry','','',{deviceOfflineFunction: function() {   }});
    	
             setTimeout(function(){
                  {dialog.object}.panelSetActive('PANELCARD_LIST',true);
    	
    	      {dialog.object}.refreshListData('FIXENTRIES');
            }, 500);
    	}
    });
    You could also move the {dialog.object}.panelSetActive('PANELCARD_LIST',true); and {dialog.object}.refreshListData('FIXENTRIES'); into an action javacript and call the action JS at the end of your xbasic function using {dialog.object}.runAction('My_Action_Name');.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Javascript timing issue

      Thanks Mike. The action JS didn't work for some reason. But the setTimeout worked well. However; I guess it could fail as it's only waiting for x amount of time vs. waiting for an action to complete.
      Alpha 5 Version 11
      AA Build 2999, Build 4269, Current Build
      DBF's and MySql
      Desktop, Web on the Desktop and WEB

      Ron Anusiewicz

      Comment


        #4
        Re: Javascript timing issue

        I love setTimeout... it solves a lot of little issues. But... in this case you don't really know how long the Ajax Callback is going to take... and if your refresh depends on the callback doing it's work, then you may be in trouble if something out there gets busy. I feel you're better off putting your JS methods into a JS function. Then, return a call to that function from your Ajax Callback. This way you know for sure that your JS will run only after your callback is complete. There's also a client-side event which fires after the callback completes in which you can test for the type of callback and other stuff. In this case you don't really need that, but it's nice to know about.

        Comment


          #5
          Re: Javascript timing issue

          since I do not have version 12 this will, probably totally, be wrong, but curious as I am..
          can you break the calls in two different places. like
          call the ajaxCallback where you have it currently. then whatever needs to be done when that callback is finished put those functions in
          the afterAjaxCallbackComplete event on the clientside?
          that will not depend on the timing?

          ps: just noticed david also suggested that.
          thanks for reading

          gandhi

          version 11 3381 - 4096
          mysql backend
          http://www.alphawebprogramming.blogspot.com
          [email protected]
          Skype:[email protected]
          1 914 924 5171

          Comment


            #6
            Re: Javascript timing issue

            Thanks for the feedback. In this case I'm stuck working with a dbf table. The good thing about this is that I have to write my own enter code and put it in the afterDialogValidate event. I say good as I can use the xbasic_wait_for_idle() function and then fire an e.javascript command. Now timing is not an issue.

            Code:
            'debug(1)
            
            ''enter the new record
            dim t as p
            t = table.open("[PathAlias.ADB_Path]\wodesclabor_m_entry_mech1")
            t.enter_begin(.t.)
            t.name = w_upper(e.datasubmitted.name)
            t.site = upper(e.datasubmitted.site)
            t.initials = upper(e.datasubmitted.initials)
            t.pw = e.datasubmitted.pw
            t.enabled = e.datasubmitted.enabled
            t.admin = e.datasubmitted.admin
            t.user = e.datasubmitted.user
            t.enter_end(.t.)
            t.close()
            
            xbasic_wait_for_idle()
            
            e.javascript = "{dialog.object}.refreshListData('USERS')"
            Alpha 5 Version 11
            AA Build 2999, Build 4269, Current Build
            DBF's and MySql
            Desktop, Web on the Desktop and WEB

            Ron Anusiewicz

            Comment


              #7
              Re: Javascript timing issue

              e.javascript is exactly the same as returning javascript commands from an Ajax Callback... same process. You're setting the property of an object which Alpha understands... and understands what to do with. Knowing you were working with DBF would have helped a bit. Although, an Ajax Callback would still be appropriate, I believe. Either way, you're just executing XBasic code and return javascript.

              Comment

              Working...
              X