MsgBox - Esc key hit

[nitekram]

I am trying to make sure that a user does not by pass a MsgBox by hitting the Esc key. Not sure if I just need to create my own GUI, or if it is possible to determine if Esc was hit.

Local $iReturn = MsgBox(0,'Test', 'Do not hit ESC key!')
If @error Or $iReturn <> 1 Then
    MsgBox('','','')
Else
    Exit
EndIf

 

 

[Damein]

Not quite sure what the 

If @error Or $iReturn <> 1 Then
    MsgBox('','','')
Else
    Exit
EndIf

Function is suppose to do (Never used it, sorry) but I believe what you can do is use the _IsPressed() function like so.

 

#include <Misc.au3>


Local $hDLL = DllOpen("user32.dll")

Local $iReturn = MsgBox(0,'Test', 'Do not hit ESC key!')

;~ If @error Or $iReturn <> 1 Then
;~     MsgBox('','','')
;~ Else
;~     Exit
;~ EndIf

Func _EscapePressed()
    MsgBox(48, "Error", "You pressed ESC!")
EndFunc


While 1
    If _IsPressed("1B", $hDLL) Then
        _EscapePressed()
    EndIf
WEnd


DllClose($hDLL)

 

*** EDIT ***

Just realized though that this will make it so ANYTIME you press ESC this happens. I doubt you want that. So maybe do something like..

#include <Misc.au3>


Local $hDLL = DllOpen("user32.dll")

$MsgBoxActive = 1
Local $iReturn = MsgBox(0,'Test', 'Do not hit ESC key!')

;~ If @error Or $iReturn <> 1 Then
;~     MsgBox('','','')
;~ Else
;~     Exit
;~ EndIf

Func _EscapePressed()
    MsgBox(48, "Error", "You pressed ESC!")
    $MsgBoxActive = 0
EndFunc


While 1
    If _IsPressed("1B", $hDLL) AND $MsgBoxActive = 1 Then
        _EscapePressed()
    EndIf
WEnd


DllClose($hDLL)

 

Edited October 10, 2015 by Damein

[nitekram]

Not sure if I explained it quite right...I basically do not want the user to be able to Esc out of the MsgBox without hitting the OK button, or whatever button is needed to continue. If I put a function to look for Esc Keys, every time the user hits the Esc key that function will run, even if it does not pertain to my script.

The reason for the code:

If @error Or $iReturn <> 1 Then
    MsgBox('','','')
Else
    Exit
EndIf

Is in the example above, if you hit the OK but, the return value should be 1, based on the help. After I can figure out how to see the Esc key, from the message box, I will create a loop that keeps posting the MsgBox until the right button is pressed.

[Damein]

Oh, well then how about this?

 

#include <Misc.au3>


Local $hDLL = DllOpen("user32.dll")

$MsgBoxActive = 1
While $MsgBoxActive = 1
    Local $iReturn = MsgBox(0, 'Test', 'Do not hit ESC key!')
    If _IsPressed("1B", $hDLL) Then
        $MsgBoxActive = 1
    ElseIf $iReturn = 1 Then
        $MsgBoxActive = 0
    EndIf
WEnd



DllClose($hDLL)

 

Now it will close out the MsgBox/Script at the moment if the "X" is clicked as well. Not sure if that factors into your idea but yeah.

Edited October 10, 2015 by Damein

[Melba23]

nitekram,

You could always use my ExtMsgBox UDF - that returns as follows:

; Return values .: Success: Returns 1-based index of the button pressed, counting from the LEFT.

;                           Returns 0 if closed by a "CloseGUI" event (i.e. click [X] or press Escape)
;                           Returns 9 if timed out
;                           If "Not again" checkbox is present and checked, return value is negated

So it is easy to check what the user did.

M23

[Damein]

But of course Melba the almighty swoops in with the better answer

[nitekram]

nitekram,

You could always use my ExtMsgBox UDF - that returns as follows:

; Return values .: Success: Returns 1-based index of the button pressed, counting from the LEFT.

;                           Returns 0 if closed by a "CloseGUI" event (i.e. click [X] or press Escape)
;                           Returns 9 if timed out
;                           If "Not again" checkbox is present and checked, return value is negated

So it is easy to check what the user did.

M23

I figured it would be something like that - I knew you had created it, but thought it might be available in the native MsgBox - as it has to return something, and in my example the Esc key actually returns 1, which is the same thing as hitting the OK button (along with hitting the X in the upper right hand corner). I would think that this might be a bug, in the function, as the button was not actually pressed?

Edited October 10, 2015 by nitekram

[water]

When checking the help file to solve this problem I noticed two stars next to

TRY AGAIN **     $IDTRYAGAIN (10)
CONTINUE **      $IDCONTINUE (11)

Does anyone know what this stars stand for? The help file doesn't explain what they represent.

[nitekram]

From reading @Melba23 post, on his UDF...this might be a limitation of Windows, but feel that if that is the case, they messed up. If a button is there, and it is bypassed, and in this case bypassing it actually clicks the button, in this case the OK button, I feel an Esc key press or a click on the red X, would be a cancel, not an OK?

 

Edit - grammar (2)

Edited October 10, 2015 by nitekram

[Melba23]

nitekram,

I imagine their argument would be that a MsgBox with a single button is a pure notification and it matters not which method is used to clear it. Have you checked to see if the same is true when there is more than the single button and the user has to make a choice?

M23

[nitekram]

By the way @Melba23, if this is indeed the case, it is a Windows issue, I vote to have your function added to the program as a replacement for MsgBox, or at the very least, have it in the program as an alternative - with help file entry and the whole nine yards (sorry if you do not understand that saying).

[nitekram]

nitekram,

I imagine their argument would be that a MsgBox with a single button is a pure notification and it matters not which method is used to clear it. Have you checked to see if the same is true when there is more than the single button and the user has to make a choice?

M23

Just tested that...I will change my code to a Yes|No and then there is no Esc key allowed...thanks for pointing this out.

 

P.S. I already changed the code with your function, so I will leave it for now, but would maybe like to see that in the help file, along with what @Water asked about with the ** in the help file.

Edited October 10, 2015 by nitekram

[Melba23]

nitekram,

the whole nine yards (sorry if you do not understand that saying).

I do indeed understand it - and have had many a discussion about its origin. However, I see that Wikipedia appears to have a new explanation - I wonder how long that one will last.

M23 

[nitekram]

nitekram,

I do indeed understand it - and have had many a discussion about its origin. However, I see that Wikipedia appears to have a new explanation - I wonder how long that one will last.

M23 

You know, I have never even looked it up. I just assumed that I knew what it meant, and I believe I have a grasp of it, but had no clue how many people have discussed its origin: I actually like the urban one, as that kind of makes sense if indeed there was a bullet belt nine yards long - "give them hell" comes to mind. But alas, it cannot be so, if other people used it before WWII - I think I read 1907 was the first print of the saying.

http://www.phrases.org.uk/meanings/the-whole-nine-yards.html

http://www.snopes.com/language/phrases/nineyards.asp

http://www.urbandictionary.com/define.php?term=Whole+nine+yards

 

[BrewManNH]

With the MsgBox function, from any language, the ESC key has the same return result as hitting the Cancel button or exiting the MsgBox by hitting the X in the window.

You'll notice that the MsgBox when used with, for example $MB_YESNO (4), there is no cancel button, and there is no X to close the window. Hitting ESC does nothing with this type of MsgBox. You'll also notice that on the one button MsgBox using $MB_OK (0), that hitting ESC returns 1, not sure what the rationale for that is, but that's how Microsoft desinged it.