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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Message Box w/o buttons?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Message Box w/o buttons?

    I want to display a small message box or window telling the user "Updating please wait" w/o buttons.

    It just inform the user w/o me having to stop the execution of the script waiting for the user to push the OK button.

    Any suggestions are welcome :)
    Mike
    Tags: None
    #2
    RE: Message Box w/o buttons?

    This functionality is usually accomplished by placing a text box in an empty area of a form, setting the text of the text box to "", then manipulating the text box's text property appropriately.

    Like

    hourglass_cursor(.t.)
    Info_box.text = "Importing file"
    Info_box.refresh()
    DIM operation_name as c
    operation_name = "Import AWG Data"
    IF operation_name "" "" THEN
    import.run_silent(operation_name)
    END IF
    Info_box.text = "" 'or Info_box.text = "Finished"
    Info_box.refresh()
    hourglass_cursor(.f.)

    where "Info_box" is the object name of the text box on the form. If you run multiple scripts or operations which need to consecutively change the message the Info_box.text = "" is useful after each to make sure the text is cleared before the new message is displayed.
    There can be only one.

    Comment

      #3
      RE: Message Box w/o buttons?

      Mike,

      While Stan's suggestion is an excellent one, one other approach is to build a "PleaseWait" UDF. This is explained in the thread:

      http://msgboard.alphasoftware.com/alphaphorum/read.php3?
      sortby=lastreply&direction=desc&num=7&id=590&thread=590

      While the initial suggestion by Jerry Brightbill is simply a box with the text "Please Wait" within it, some supplement variations you will see include explanatory text (e.g. "Please Wait - Calculating Total Cost"). We use the latter extensively.

      Steve

      Comment

        #4
        RE: Message Box w/o buttons?

        Thanks for the help guys. It gave me a place to start.

        BTW, link is broken :).

        Thanks,
        Again

        Comment

          #5
          RE: Message Box w/o buttons?

          Actually, the link is good but extra spaces/line-feeds get mixed in when you cut and paste it.

          Try this: Link to PleaseWait function from Jerry Brightbill

          Cal Locklin
          www.aimsdc.net

          Comment

            #6
            RE: Message Box w/o buttons?

            What about the Wait Dialog command. Thats what I use to inform the user something is going on. You have several different options such as a percentage done or just a plain message. Is there a reason this is not suggested ?

            Just wondering if I am missing something
            Jason

            Comment

              #7
              RE: Message Box w/o buttons?

              Is there a reason? Yes. My reason is that there are so many new features I sometimes forget about the new stuff because I'm so used to the old stuff.

              Jerry came up with a very good PleaseWait function in v5 and I'm so used to using it that I forgot about the new function available in v6. My guess is that Stan and Steve forgot about it, too. (Many of my customers still use v5 so I can't just wipe the "old stuff" out of my head.)

              After having just tested the new function, another reason might be that no matter how hard I try I can't get the Cancel button to work on the Wait Dialog. Even the example in the Help file doesn't close - the button is there but it doesn't do anything. One thing that I found to be critical on my PleaseWait_fnc function (Jerry's function as modified for my use) was to make it possible to close the dialog if the script crashed for any reason. When a remote customer runs into a problem, they may need some way to close the message window other than shutting down the program. It seems to me that the only way to close the Wait Dialog if the script crashes is to shut down A5 and restart it. Anyone have a solution?

              Cal Locklin
              www.aimsdc.net

              Comment

                #8
                RE: Message Box w/o buttons?

                Cal,

                I abandoned the WaitDialog function for the same reasons and am posting this response for other forum members who may be reading this topic string. Sometimes the cancel would work and other times not. Indeed, there is no way to close the dialog if the script does not complete successfully.

                The solution to getting rid of the WaitDialog is to drag it off the screen! But that's not acceptable for your application users. A modeless dialog with a progress bar works best and the ui_modeless_dlg_refresh command makes it convenient to update the progress message.

                I like the concept of the WaitDialog and how you can employ it with a lot less programming. I hope Alpha will beef this up for future releases.

                Deene

                Comment

                  #9
                  RE: Message Box w/o buttons?

                  Take a look at the WaitDialogQD class, which is a bit more robust....it's still a bit of a work-in-progress, but it mostly does the trick.
                  Aaron Brown
                  Alpha Software Development Team

                  Comment

                  Previous template Next
                  Working...
                  X