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

Disabling Xdialog Buttons

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

    Disabling Xdialog Buttons


    A common practice in an xbasic onPush event script for a button is to disable the button at the top of the script, and then enable it at the bottom of the script. This prevents a nervous / frantic / wired user from inadvertantly running the script twice with a rapid double click.

    Question: Is something like this prudent for xdialog buttons, also? If so, could someone post an example of how it's done?

    I ask because in rare circumstances I've seen quick double clicks on a simple OK button run the remaining script twice. i.e. if an OK click branches to code that opens a form, I've seen the form open twice.

    -- tom

    #2
    RE: Disabling Xdialog Buttons

    Tom:
    "" ..branches to code that opens a form, I've seen the form open twice. ""
    A good idea is to use if_is_object() to prevent opening more than one copy of the same form (or browse)
    Gabe

    Comment


      #3
      RE: Disabling Xdialog Buttons

      meant to say:
      if is_object("form_name")
      then
      form_name.show()
      form_name.activat()
      else
      form_name.view("form_name")
      end if
      Gabe

      Comment


        #4
        RE: Disabling Xdialog Buttons

        I've never seen an issue with this Tom. And I don't think there is any way to disable the button like you are doing on forms.

        Cal Locklin
        www.aimsdc.net

        Comment


          #5
          RE: Disabling Xdialog Buttons

          Tom

          As Cal suggests, I have not seen this as a big issue. The script would have to be very lengthly to be a problem. But you could easily disable a button in xdialog while the code was running. For example, the following line has an event and an enabled code

          "*15=ok_button_label!OK?show_ok"

          Before the xdialog runs, you set show_ok = .T. In the event code you might have something like this

          if a_dlg_button = "ok"
          a_dlg_button = ""
          show_ok=.F.
          'your script
          show_ok=.T.
          end if

          It works, but looks a bit odd as the button appears as stuck in the depressed state until it is enabled again. You could also use the old method for the "maximum stack depth exceeded" error message. That works for any button or script in any location.

          Jerry

          Comment


            #6
            RE: Disabling Xdialog Buttons

            Thanks to all.

            -- tom

            Comment


              #7
              RE: Disabling Xdialog Buttons

              Cal & Jerry:
              On first glance, this does not appear to be a big issue, but it could be, How so?
              Most buttons on most xdlg boxex will execute a script then shut down the box as in most cases of the OK, Cancel, Close.
              But in other instances, you would like to keep the box open to execute multipe actions. A begnin example: navigation buttons: back, next, continue. If you run the script more than once in any one of these buttons, you would not cause much damage but in other circumcetances you will. In the example Tom provided, you could open more than one instance of the same form, which still not a very major problem, but take this example: I have a xdlg to enter transactions (payments made). In most cases I enter more than one transaction at a time which means I would like to keep the box open until I choose to close it. Now, if you click the Save Transaction button twice, you could end up with a duplicate of the same transaction. Not good.
              Alpha does provide for disabling butons on the xdlg: simply grey it out.
              Gabe

              Comment

              Working...
              X