Improve LotusScript debugger Merged

One cause for the debugger not showing the line actually executing is lines with multiple statements separated by a colon. Please fix

It would be useful to be able to start the LS debugger at a certain event, like a button click, so you don't have to go through all the QueryOpen events and such.

Also wouldn't mind syntax coloring and font control. Helps a great deal in spotting the breaks between modules.

Also:

• When displaying/editing the value of a variable, special characters such as "newline" are not represented, and a "tab" character in the data messes up the display.
• Variable values don't always update when the variable's value changes.
• Sometimes the debugger halts on a line where no breakpoint has been set. Every. damn. time that line is executed.
• It would be great to have a way to DISABLE stopping on a Stop statement, e.g. by putting a disabled breakpoint on that line. Sometimes a Stop in an inconvenient place can make debugging very slow because it stops way to often where you didn't want it to.
• Occasionally, when starting debugging, the debugger grabs focus but doesn't open/come to the front. Clicking around in the client and Designer windows doesn't help. Alt-tab doesn't work. You have to select the debug window from the Windows task bar and then click on it. Something like that. It is, at any rate, the opposite of smooth.
• There needs to be a database property to disable use of debugging in that application. Not only because 63% of the time I'm debugging something, I accidentally debug my mail file, but because it's easy for users with the Designer client to bypass controls in production applications by debugging LotusScript and adjusting variable values or simply aborting the Querysave code that was supposed to prevent them from saving invalid data.
• Often when debugger is active, and I create a memo (because I forgot debug was on), the memo opens in the debugger client window instead of in Notes, and everything is locked up -- must terminate Notes processes.
• People who write object-oriented LotusScript find it difficult to locate the line they want to set a breakpoint on because unlike the editor, all the classes are lumped together in the Declarations section.
• It would be excellent to be able to search the source code that you're debugging.
• Ability to set a breakpoint based on an expression -- when a variable has a specified value -- would be helpful.
• Built-in performance profiling would be great!
• The menu state of the debugger in Designer is sometimes wrong, e.g. when you turn it on in Designer, but turn it off in the client, Designer doesn't notice it's off.

https://domino.ideas.aha.io/ideas/DDXP-I-8

More than 256 items displayed in a document

add SEARCH function in the object tree window

when you open 'items' you see [0], [1], [2]...[n] ...on the right. it should be the item name

the values of the item should be shown (on the right side) as first in the object tree

or the opposite of what Theo suggests with 4:
"Debug LotusScript" shall only debug the current application

1b: Sort the field names within document.items

4. Have a DB option to disable debugging into it, when you are debugging another app (e.g. your own email)