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

Wait_until

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

  • Wait_until

    Hello

    I want to check a form (or Non-A5 Windows) is opened or not with Wait_until().

    I have attached the code.
    Code:
    ' a form or Non-A5 window is already opened and It is an xdialog.
    vlayout = "sample form"
    vResult = .f.
    vflag = file_is_open(vlayout)
    ' or   vflag = is_object(vlayout)
    
    If vFlag = .t.    'The FILE_IS_OPEN() function returns .T. (TRUE) if a file is open.   but I could not get " .t. " statement when it is opened.
        vCheck ="Opened"
    else
        vCheck="closed"
    end if
            
    vResult = wait_until(vCheck ="closed",1,2)  'Does wait_until should runs again after 2 second later?
    
    If vResult = .t. then        
         msgbox("still opened ")
    else
        msgbox("closed ", "after closed, open another form or xdialog ")
            
    end if
    Does wait_until should runs again after 2 second later until the condition, vCheck="closed" , is .t. statement ?
    Last edited by johnkoh; 09-24-2014, 07:52 PM. Reason: not completed

  • #2
    Re: Wait_util

    Nope
    Code:
    If vResult = .F. then        
         msgbox("still opened ")
    else
        msgbox("closed ", "after closed, open another form or xdialog ")
    end if
    When the time elapses the next line will execute but vResult will reflect the status of the wait condition at the time of release

    end if

    Comment


    • #3
      Re: Wait_until

      Hi Ray,

      vResult will reflect the status of the wait condition at the time of release
      Then How would you write for checking the form is opened or not until closed it?

      Comment


      • #4
        Re: Wait_until

        Are you trying to pause a script until an xdialog is closed or are you trying to trigger some code when the xdialog is closed?
        There can be only one.

        Comment


        • #5
          Re: Wait_until

          Hi Stan,

          are you trying to trigger some code when the xdialog is closed?
          Yes, This is what I want to do.

          Comment


          • #6
            Re: Wait_until

            Why not just code the xdialog?

            Code:
            ui_modeless_dlg_box("Name",<<%dlg%
            Name: [.20name];
            {lf};
            <Close>;
            %dlg%,<<%code%
            if a_dlg_button = "close" then
               msgbox("Closed")
               ui_modeless_dlg_close("name")
               end
            end if
            %code%)
            There can be only one.

            Comment


            • #7
              Re: Wait_until

              On the matter of using wait_until
              You just had the logic wrong way

              Comment


              • #8
                Re: Wait_until

                Stan,

                I have few different case to apply this action (checking opened or closed a Form).

                case 1: Started from xdialog -> Display the records with pdf -> after work with a PDF and closed this pdf window -> **When PDF window is closed then Trigger other action, example -- open an xdialog, ask printed it good or not -> Re-Open the PDf window again or store the Print result to table **

                case 2: Started from xDialog(*it is not Modeless dlg) -> Open A5-Forms but I have the problems at here,

                (1) not able to activate a A5-Form without close an xDialog The Ui_dlg_Hide() did not hide the xDialog
                (2) If I closed an xDialog, How do I open again an xDialog after closed A5-Form?
                (2-a) What If My A5-Form's Close Button is included the open an xDialog and another A5-Form actions, How do I know the condition that it was opened by an xdialog or other form?


                On case 2, I think the solution is that I have to change to Modeless - xDialg from standard xDialog. I have not tried it yet and am still working with case 1.

                Thank you

                Comment


                • #9
                  Re: Wait_until

                  Ray,

                  I choose Wait_Until() because, from Help
                  Alpha Five checks the Logical_Expression every Every_N_Seconds.

                  Comment

                  Working...
                  X