I was not aware that I had to submit an idea for my comment.

Here is some extra comment:

Last time I asked for a function to test whether or not debug mode is on. What about a function to set debug mode on? This can be very useful when you want to trace what is happening with your code when document number 1000 is handled and you dont care about the previous 999 doucments.

debug scope ought to be at a database level.

I'd also like to see debug directives that prevent or force debugging at procedure level

Very nice idea.

Thanks - yeah, the debug directive "stop" (if you could call it that) doesn't cut it for me!

I also think we need to be able to set breakpoints within the designer IDE code editor itself (and yes, for gods sake deprecate LotusScript's "Stop"), and by default the debugger should only activate when any executing code hits a breakpoint. Isn't this how Visual Studio, Eclipse and the like operate?

Sounds like an idea that I had a couple of years ago and even created screen mock up of { Link }

So yes, I like the idea

@2: Could be impractical with multi-db applications where execution can bounce around a bit. Perhaps a blacklist would be better.

As for Stop - using a global constant in a low-level library to do something like

If DEBUGLEVEL > 0 Then Stop

usually works for me.

I hate to think how many hours I have probably accumulated in lost productivity checking my mail whilst the debugger is still on and having to step through all the mail events.

Why not asking the user, if he wants to debug all or current application, when he activates debugging.

Like breakpoints, he could activate debugging for more than one application and can be presented a list of applications in debug mode, when deactivating debug: only current app, all apps or select in list.

And while we are on debugging.
- Conditional breakpoints would save lots of time.
- Variable Watchlist are another thing missing.

Variable watchlist is big as is @1 and@5.

It would be nice if my breakpoints actually persisted. I've got the setting on but they frequently disappear.

@6 - Chad Schelfhout -

You are going to have to eclipsify that mock up, but yeah, that would do it!

A couple of possible additions:

-database property and / or code to prevent debugging
-policies to control who can update and / or populate the lists

and while we're on the subject, can we get a keyboard shortcut already?!

I to would like to see debug scope at the database level
It's a royal pain in the rear when in debug on my test app to have to look in help or to email someone

Yes! Debug option should be per database, and not everything. That would really speed up my debugging process.