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

Sleep or xbasic_wait_for_idle

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

    Sleep or xbasic_wait_for_idle

    We have developed a routine to scan (sometimes very large) documents to a file using Alpha 5 and a twain driver.

    This has been working very well for years.

    Recently we deployed new, very fast DELL all-in-one desktops with Windows 10.
    Since deployment, this particular routine has been hanging up after scanning during the process to build the pdf we eventually want to save.
    My thoughts here are that the code loop to add each scanned image to the pdf may be running faster than the add to pdf function.

    So, the question is do we just put a sleep() in after the add to pdf, or an xbasic_wait_for_idle()

    the loop is pretty simple.
    Code:
    for j = 1 to tw.imagecount 
    	tw.selectedimage = j
    	tw.addtoPDF(0)
    next j

    Any thoughts would be appreciated.

    Tom

    #2
    Re: Seep or xbasic_wait_for_idle

    I seem to remember Jerry Brightbill saying they were the same thing. Having said that, I never liked Sleep() and always seemed to get good results with xbasic_wait_for_idle().
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Seep or xbasic_wait_for_idle

      Thanks, Peter.

      We'll give it a try in the morning.

      Tom

      Comment


        #4
        Re: Sleep or xbasic_wait_for_idle

        I always thought that sleep() was a modal execution that stopped the script from moving forward and a pause between the execution of line of script in which it resided and the next line, while xbasic_wait_for_idle was modeless but "sensed" the execution of the prior command and when the prior command was complete allowed proceeding through the script. To that end, I have always used xbasic_wait_for_idle(). Except I have found that there are events that neither work, but inserting a call to a modeless xdialog that opens for a fraction of a second and closes introduces a pause or deviation in the script that makes the difference for a script to paint or refresh things successfully, which I have in my armament as dlg_blink(). There are places that absolutely require dlg_blink() for the script to work.
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment


          #5
          Re: Sleep or xbasic_wait_for_idle

          This might work:

          Code:
          dim LV as p = local_variables()
          
          for j = 1 to tw.imagecount 
          	addimg(j,lv)
          next j
          
          function addimg as V(x as N,Var as P)
          	WITH Var
          	tw.selectedimage = x
          	tw.addtoPDF(0)
          	xbasic_wait_for_idle(.15)
          	END WITH
          end function
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


            #6
            Re: Sleep or xbasic_wait_for_idle

            Tom, I'm not familiar with the addtoPDF() method you are using. However, you should consider creating a UDF on the code page. Then call it from inside your loop, passing necessary pointers to the UDF on each trip through the loop. The For...Next loop will stop while the called UDF executes. [ edit: I see now that Robin has the same sort of idea, without using the Code page or a global UDF. it seems likely to me that he need not include the wait_for_idle inside the AddImg() function.]

            Comment


              #7
              Re: Sleep or xbasic_wait_for_idle

              Robin and Tom,

              I haven't been back to the forum in a couple of weeks, and just today I saw your posts. As the users are still having issues, I will do as you have shown.
              Tom, The addtoPDF function is part of the twain control software. We're using Ciansoft's TwainControlX.twain. It has a lot of functionality and for the most part, it works just fine.
              With our older machines, we didn't have a problem, however with the newer, much faster windows 10 Dell all-in-one's, we are now seeing a problem.
              Thanks.

              Tom

              Comment

              Working...
              X