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 detect when closing an XDialog with Red X

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

    How to detect when closing an XDialog with Red X

    Specifically, how can I make the red X in the title bar of an XDialog box work the same as my Cancel button? In other words, in my cancel button, I have a confirmation dialog to ask the user if they are sure they want to abandon changes. But closing with the red X simply closes the dialog with no prompt whatsover.

    I have tried to trap for varC_result="" , which is the value closing with the red X sets it to. But this works fine after the dialog already has closed, but seems to interfere with the normal event handling routines I have if I try to do this in the %code% section. Seems this should be relatively easy, but I am not seeing it.

    If anyone has any ideas for me I would greatly appreciate the help. Thanks.

    #2
    Re: How to detect when closing an XDialog with Red X

    I don't know that you can trap the red-x close. Instead, when I need to force something like you do, I make it a ui_modeless_dlg_box. This disables the red-x, and then you need to provide your various buttons and control code.
    -Steve
    sigpic

    Comment


      #3
      Re: How to detect when closing an XDialog with Red X

      You can have the red-x not appear if you make the first command of the ui_dlg_box() be
      {toolcaption}

      Contrast the behavior of

      Code:
      ui_dlg_box("Xdialog Sample", <<%dlg%
      <30,2 Sample>;
      %dlg%)
      with

      Code:
      ui_dlg_box("Xdialog Sample", <<%dlg%
      {toolcaption}<30,2{TOOLCAPTION} Sample>;
      %dlg%)
      There can be only one.

      Comment


        #4
        Re: How to detect when closing an XDialog with Red X

        Thanks Stan, I learned something today. Now if I could only take the rest of the day off....
        -Steve
        sigpic

        Comment


          #5
          Re: How to detect when closing an XDialog with Red X

          Stan,

          I like that solution much better than having the red X visible and having to duplicate some code somewhere.
          Thanks very much!

          Gordon

          Comment


            #6
            Re: How to detect when closing an XDialog with Red X

            By the way, is there a reason you repeated the {toolcaption} command more than once?
            it seems to do the job with only one in it...

            Comment


              #7
              Re: How to detect when closing an XDialog with Red X

              I copied the sample from the help files. (local)
              Last edited by Stan Mathews; 10-07-2011, 03:08 PM.
              There can be only one.

              Comment


                #8
                Re: How to detect when closing an XDialog with Red X

                Looks like it should be

                Code:
                ui_dlg_box("Xdialog Sample", <<%dlg%
                {toolcaption}<30,2Sample>;
                %dlg%)
                There can be only one.

                Comment


                  #9
                  Re: How to detect when closing an XDialog with Red X

                  Thanks again Stan. Wasn't sure if there was something I was missing.

                  Comment


                    #10
                    Re: How to detect when closing an XDialog with Red X

                    Actually as the example from the local help is executed the xdialog result is

                    Code:
                    rslt = ui_dlg_box("Xdialog Sample", <<%dlg%
                    {toolcaption}<30,2{TOOLCAPTION} Sample>;
                    %dlg%)
                    
                    
                    ? rslt
                    = "{TOOLCAPTION} Sample"
                    Likely not what is wanted.

                    I think the wiki example is better.

                    'A standard modal Xdialog. (escape to exit)

                    ui_dlg_box("Toolcaption Test",<<%dlg%
                    {toolcaption}
                    This is a modal dialog with the \{toolcaption} command.;
                    Notice that it does not have the red X button in the title bar.;
                    ;
                    %dlg%)
                    Last edited by Stan Mathews; 10-07-2011, 04:34 PM.
                    There can be only one.

                    Comment


                      #11
                      Re: How to detect when closing an XDialog with Red X

                      Of course you can run code with a red X of an Xdialog.

                      Just use the code below in the Xdialog body substituting your xdialog event name, and place the code in the XDialog event handler. An example is in the code archive here that actually shows usage.

                      {can_exit=xdialog_event_name}
                      Regards,

                      Ira J. Perlow
                      Computer Systems Design


                      CSDA A5 Products
                      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                      CSDA Barcode Functions

                      CSDA Code Utility
                      CSDA Screen Capture


                      Comment


                        #12
                        Re: How to detect when closing an XDialog with Red X

                        And if you want to trap the red X, you might also want to stop someone from using the ESC key. Use {On_Key=ESC} to do that.

                        Oops. This may not be necessary in v10. I seem to recall that they changed from "The ESC key closes the xdialog unless you write code to keep it open using {On_Key=ESC}" in previous versions to "The ESC key doesn't close the xdialog unless you add code to close it using {On_Key=ESC}". This is the kind of thing that can drive you crazy when working with multiple versions of A5. Oh well, it's still good to know how to control what happens with the ESC key.

                        Comment


                          #13
                          Re: How to detect when closing an XDialog with Red X

                          Escape still closes one in V10 for me.
                          There can be only one.

                          Comment


                            #14
                            Re: How to detect when closing an XDialog with Red X

                            Originally posted by Stan Mathews View Post
                            Escape still closes one in V10 for me.
                            Thanks Stan. That doesn't surprise me. It was late so I didn't check before posting but remembered running into some cases where the xdialog didn't close the way I expected it to by default. I thought it was a difference between versions somewhere but I could be wrong. Mostly that was a disclaimer. The basic point is that, either way, it can be controlled with the {On_Key=ESC} command.

                            Comment


                              #15
                              Re: How to detect when closing an XDialog with Red X

                              Hi Cal,

                              In general, from a user interface point of view, an escape should not close a dialog box. The reason is, if the key auto-repeats, it will close the current dialog, then the dialog before it, and the next to the number of escaped pressed. Assuming the dialogs need to be handled, or viewed, this may be incorrect behavior,

                              On the other hand, if subsequent escape keys are not an issue, then being able to escape the dialog is useful for the user.
                              Regards,

                              Ira J. Perlow
                              Computer Systems Design


                              CSDA A5 Products
                              New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                              CSDA Barcode Functions

                              CSDA Code Utility
                              CSDA Screen Capture


                              Comment

                              Working...
                              X