Problem w/PBCC5

[Walt Decker]

I'm using XP PRO SP2. When I click on the console system button I receive a message that windoz cannot shut down the program. This does not happen with PBCC4. Has anyone else experienced this?

[Bob Zale]

#BREAK ON

Read all about it...

[Mike Doty]

Deleted

[Walt Decker]

Thank you, Bob.

However, I've run into another problem. With PBCC4 in DEBUG mode the debug window used to remain active when in "run" mode. That is not the case with PBCC5. Is there a way to keep the debug window active so that the program can be stopped at any point regardless of whether there is an error?

[Bob Zale]

We did that to vastly speed up debug execution over large sections of code without breaks. If you must have a break from the keyboard, just GOTO Window/Options/Compiler and click "Break on error". That forces the debugger to stop and check on every line of code.

[Walt Decker]

Thanks, Bob.

I did that but then it breaks on every error regardless of whether there is an error trap. Oh well, with all the nifty things in the PB products, I can live with that.

Thanks again for the info and the fine products you produce.

[Mel Bishop]

Thanks for that info Bob. You can disregard the e-mail I sent to support concerning this matter.

[Michael Mattias]

More programmer control over this kind of thing: SetConsoleCtrlHandler() WinApi function.

I know there are examples here.