: 4582 | 108668 | 12353

Application (Database) Block List for Debugger 
Use this IdeaSpace to post ideas about Domino Designer.

: 79
: 79
: 0
: Domino Designer
: debugger, client, designer
: Joseph Hoetzl4703 26 Mar 2008
: / Email
As the user, designer, administrator of our Notes environment, I frequently have all 3 loaded. 
I'd really like an app/db block list so that when I have the "Debug Lotusscript" option enabled and I need to check my mail, or something else, that I could have a list of db/apps that I could exclude from the debugger.
Maybe I am doing something completely wrong, but I don't see a away around this currently.
If there is a way to do this, please enlighten me.
I saw Rob's comment, but I didn't see an actual Idea submitted for it, and I really just got irked at this issue a little while ago...

1) Rob Goudvis6585 (27 Mar 2008)
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.
2) Paul Davies12381 (27 Mar 2008)
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
3) Bruce Elgort8320 (27 Mar 2008)
Very nice idea.
4) Joseph Hoetzl4703 (27 Mar 2008)
Thanks - yeah, the debug directive "stop" (if you could call it that) doesn't cut it for me!
5) Jeff Gilfelt1049 (27 Mar 2008)
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?
6) Chad Schelfhout146 (28 Mar 2008)
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
7) Morten Clausen421 (28 Mar 2008)
@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.
8) Peter Presnell26659 (01 Apr 2008)
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.
9) Thomas Bahn3674 (12 Apr 2008)
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.
10) Thomas Schulte725 (15 Apr 2008)
And while we are on debugging.
- Conditional breakpoints would save lots of time.
- Variable Watchlist are another thing missing.
11) Jordan Tenjeras1232 (15 Apr 2008)
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.
12) Joseph Hoetzl4703 (24 Apr 2008)
@6 - Chad Schelfhout -

You are going to have to eclipsify that mock up, but yeah, that would do it!
13) David Dickey24 (13 May 2008)
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?!
14) Christopher Boote6132 (11 Aug 2009)
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
15) Christian Heroe533 (11 Mar 2011)
Yes! Debug option should be per database, and not everything. That would really speed up my debugging process.


Welcome to IdeaJam

You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.

Use IdeaJam to:

  • Collect ideas from employees
  • Solicit feedback and suggestions from employees and customers
  • Run innovation contests and competitions
  • Validate concepts
  • Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top

IdeaJam™ works with:

  • IBM Connections
  • IBM Lotus Quickr
  • Blogs and Wikis
  • Websphere Portal
  • Microsoft Sharepoint
  • and other applications.

IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.

Learn more about IdeaJam >>

IdeaJam developed by

Elguji Software Logo