Opposite of Set Step On

[RacingSoftwareGuy]

Is there a command that will cancel the Debugger?

I have issued Set Step on on one procedure and want to stop the debugger after that and close its window. Is there a command that does it?


Don Higgins

http://www.crewchiefpro.com

 

[craigsboyd]

RESUME

SweetPotato Software Website
My Blog

 

[JimWWinter]

Hi Don,

Close the debugger and key in Ctrl + M.

Jim

 

[Mike Lewis]

Don,

Either type RESUME in the command window (as per Craig's suggestion) or click the Resume button in the debugger's toolbar.

You don't need to close the debugger, but you can if you want (your app will run faster with the debugger window closed).

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[RacingSoftwareGuy]

I want to close the debugger and close the debugger window because the Skins Class runs afterwards and it takes forever in the debug mode.

Thanks for the info. I already used Resume but was just wondering if there was a command that closed the window and canceled the debugger.

No big deal, just trying to save a few keystrokes.



Don Higgins

http://www.crewchiefpro.com

 

[craigsboyd]

You could perhaps set up a macro in Visual FoxPro to handle this in a single keystroke.

SweetPotato Software Website
My Blog

 

[alvechurchdata]

If you're running the debugger within the FoxPro frame then you can use something like RELEASE WINDOW WATCH to close the window. Don't know what to do if the debugger's running as a separate process.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[DSummZZZ]

Adding to Geoff's post,
RELEASE WINDOW trace
should remove the 'STEP' window. Used in combination with 'RESUME', you should be on your way.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Mike Lewis]

Dave,

RELEASE WINDOW trace should remove the 'STEP' window

Alas, not if the debugger is running in a separate frame.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[DSummZZZ]

Mike,

Hence the addendum to Geoff's post.
I haven't tried to deal deal with releasing the debugger in a separate frame issue myself, but issuing those statements still releases the windows in the debugger. It may still speed things up.



-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Mike Lewis]

Dave,

Yes, that's true. Actually, you can still do RELEASE WINDOW TRACE, ... WATCH, ... LOCALS, etc if the debugger is in a separate frame. They will release the individual windows, but not the debugger itself (as far as I can see).

In any case, it's surely much easier just to click the X button in the debugger's title bar.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[TamarGranor]

Is CLOSE DEBUGGER the command you're looking for?

Tamar

 

[Dan Freeman]

You got there JUST before me. <g>

CLEAR DEBUG is the other one that's often overlooked.

Dan

 

[Mike Lewis]

Dan,

CLEAR DEBUG is the other one that's often overlooked.

You don't mean that CLEAR DEBUG is the same as CLOSE DEBUG, do you?

CLEAR DEBUG restores the debugger windows to their default state, and clears all breakpoints and the Watch list. It opens the debugger if it is not already open.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)