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

How to auto close an open dialog box

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

  • Stan Mathews
    replied
    Re: How to auto close an open dialog box

    That is interesting. I just tested

    {timer=CANCEL}

    and a_dlg_button is set to CANCEL when the timer expires and the dialog closes.

    Tested further and you can use anything you want in the {timer=something} directive, or so it seems.

    Reread the documentation about 5 times and finally "got it". The {TIMER} command generates timer events. When an event occurs in an xdialog, a_dlg_button is given the value of the event name. Any event that occurs, which is not trapped in the code section of the xdialog and a_dlg_button is not reset to "" will close the xdialog.
    Last edited by Stan Mathews; 09-18-2017, 04:22 PM.

    Leave a comment:


  • Tom Henkel
    replied
    Re: How to auto close an open dialog box

    Steve Andrews was playing with this, and he found that a_dlg_button is set to "close" when the timer is hit, so we can test for a_dlg_button and change the result to "Cancel" instead of OK, which will stop any code after the dialog from running.

    I always have an "If varC_result <>"OK"" after the dialog.


    Again, Stan, Thanks.

    Leave a comment:


  • Tom Henkel
    replied
    Re: How to auto cloase an open dialog box

    Thanks, Stan.

    Will have to see what affect that has on the code after the dialog closes.

    Leave a comment:


  • Stan Mathews
    replied
    Re: How to auto cloase an open dialog box

    Any selections made in the xdialog will be in effect when the xdialog "auto closes" and the xdialog result will be "OK" or whatever the normal close button returns. Not sure if you need to allow for that in what you are doing.

    Leave a comment:


  • Tom Henkel
    replied
    Re: How to auto cloase an open dialog box

    Stan,

    As usual, YOUR THE MAN!

    Thanks,

    Tom

    Leave a comment:


  • Tom Henkel
    replied
    Re: How to auto cloase an open dialog box

    Ron,

    My mistake.

    I don't open tables until all of the data is entered, verified, and the user clicks "OK". I then open, change, and close the individual tables.

    The problem seems to be that an open dialog box prevents anything else from happening. I just tested that this morning. I set my "close Alpha" script to start at a specific time via the script_schedule() function, and then opened a form, opened a dialog and left it sit.

    The scheduled time passed, and nothing happened until I closed the dialog. The scheduled script then executed, and The database closed.

    What I need to do is to have an "on-timer" routine similar to one on forms that will auto close idle x-dialogs.

    Tom

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: How to auto cloase an open dialog box

    Tom, when you say the xdialog is leaving tables open, it's really your code behind the xdialog that's leaving the tables open.

    What I try to do is to only open tables when I need to get some information and then I write that information to variables. Then I close the table.

    Then to protect the integrity of the data, I usually use similar code to the following:


    Code:
    dim MyTable as C = "logged_in"
    dim shared vRec_Before as C = ""
    dim shared vRec_After as C = ""
    dim shared vMyKey as N
    
    vMyKey = 1234	'record number of record to be changed
    
    dim t as P
    t = table.open(mytable)
    t.fetch_find(vMyKey)
    vRec_Before = property_to_string(t)
    
    'set a number of variables
    t.close()
    
    'do a bunch of stuff
    'now press the save button and save the record
    t = table.open(mytable)
    t.fetch_find(vMyKey)
    
    vRec_After = property_to_string(t)
    
    if vRec_Before <> vRec_After then
    	msgbox("Error","Someone Has Changed This Record While You Were Working On It",UI_STOP_SYMBOL+UI_OK)
    	end
    end if
    
    t.change_begin()
    t.logged_in = "Administrators"
    t.change_end(.t.)
    t.close()
    
    end

    Leave a comment:


  • Stan Mathews
    replied
    Re: How to auto cloase an open dialog box

    Immediately after varC_result = ui_dlg_box(.........<<%dlg%

    add the line {timer=close}{interval=120}

    where 120 represents the number of seconds to leave the xdialog open if it is not closed by the user.

    Leave a comment:


  • Tom Henkel
    started a topic How to auto close an open dialog box

    How to auto close an open dialog box

    We've been running into a situation where users will leave dialog boxes open and then go home. This, in turn leaves many tables and indexes open which causes them to NOT get backed up overnight.

    I already have a routine (scheduled script) that will close any open forms at a specific time at night, then close Alpha, but it seems that when an x-dialog is open, the routine won't run.

    Does anyone have a solution to auto close an x-dialog box after a specified amount of time?

    Any help would be greatly appreciated.

    Tom
Working...
X