Issue with ExitLoop in nested While Loop.

[Regravity]

I'm having an issue with using ExitLoop within a nested While Loop.

I've got basically:

GUI inside a function fired by Tray Menu [while loop]

           Button Creates Second Gui (attached to the button) [while loop]
 
                    Button to Cancel that has ExitLoop attached (does not work)

I can't see what I'm doing wrong, if I use ExitLoop(3) then it functions to close the entire application!

Please someone help!

Thanks in advance!

(P.S. I haven't posted code to protect the project I'm working on, I can post a little if needed.)

Edited June 18, 2011 by Regravity

[guinness]

Use ExitLoop to exit the current loop, ExitLoop 2 to exit first & second and then as you've been using ExitLoop 3 will exit all 3.

[Melba23]

Regravity,

It is a bit difficult to offer pertinent advice without seeing any code, but this example script shows how you use the "level" parameter with ExitLoop:

expandcollapse popup

#include <GUIConstantsEx.au3>

$hGUI = GUICreate("Test", 500, 500)

$hButton = GUICtrlCreateButton("Child GUI", 10, 10, 80, 30)

GUISetState()

While 1

    Switch GUIGetMsg()
        Case $GUI_EVENT_CLOSE
            Exit
        Case $hButton
            $Child_GUI = GUICreate("Child", 200, 200)

            $hCancel = GUICtrlCreateButton("Cancel", 10, 10, 80, 30)
            $hExit   = GUICtrlCreateButton("Exit", 10, 90, 80, 30)

            GUISetState()

            While 1

                Switch GUIGetMsg()
                    Case $GUI_EVENT_CLOSE, $hCancel
                        GUIDelete($Child_GUI)
                        ; Exit the current loop - eqivalent to ExitLoop 1
                        ExitLoop
                    Case $hExit
                        ; Exit both the current loop AND the original loop
                        ExitLoop 2
                EndSwitch

            WEnd

    EndSwitch

WEnd

As you can see, the "level" parameter refers to the number of loops to exit, not the current nesting level

Does that help?

M23

[Aktonius]

Might be that you just need to use ContinueLoop.

In any case as Melba23 said without code its hard to know what you are doing. So if you can't show it then simply memorize

ExitLoop[level] - Kills the loop

ContinueLoop[level] - Jumps straight at the loop level and skips the codethat is written after continueloop(), also skips current loop index.

I suggest that you figure this out with examples inside helpfile. It is much easier to tune the code when you understand it then blindly trying to modify something you dont fully understand.

Edited June 18, 2011 by Aktonius

[JohnOne]

Dont use ExitLoop(3)

Just ExitLoop.

[Regravity]

Dont use ExitLoop(3)

Just ExitLoop.

Yup, Yup, Tried it.

And if you had compiled the code, you would see that method also fails...

[JohnOne]

Fails what?, you dont even say whats wrong.

[Regravity]

Fails what?, you dont even say whats wrong.

Nope don't worry, I believe I've figured out the issue.

[jchd]

I've tried to try it. Something brings my attention: how do you think your child GUI behaves after you (successfully) exit the inner msg loop using ExitLoop? Of course it doesn't react to anything, but it still exists. You need to destroy/hide it.

[Regravity]

I've tried to try it. Something brings my attention: how do you think your child GUI behaves after you (successfully) exit the inner msg loop using ExitLoop? Of course it doesn't react to anything, but it still exists. You need to destroy/hide it.

Yup Figured it out.

Thanks all that helped.