Welcome to the #dominoforever Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated jointly by the IBM & HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino page.


Improve lotusscript debugger

There are various factors which make it a pain to debug lotusscript/template code for a complex template like the mail template. 

 

Some examples (adding/improving per the comments. Thanks! ): 

1. Sort the member variable names of an object, so you don't have to browse the entire list to know the value of variable you are interested in. Cannot watch variables. Perhaps add SEARCH function.

When you open notesdocument.items variable, you see the item index [0]..[n] on left side instead of the item name. So even after sorting the member variables won't be ordered in terms of item names. Suggest to sort the field names within notesdocument.items.

2. Stop debugging does not work at times.

Sometimes the debugger halts on a line where no breakpoint has been set.

3. Cannot debug lotusscript within a dialog and have to use print statements

4. Give option to disable debugging into applications other than the one you started with! Or give a debugger runtime option to skip a particular db.

5. It would be excellent to be able to search the source code that you're debugging. For example, to set a breakpoint.

6. Debugger window/menu issues

i. 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.

ii. Sometimes you need to terminate Notes to disable the debugger. The menu options of the deubgger don't allow to close it/are grayed. 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. 

iii. 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.

7. Coloring to differentiate

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 16 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 16, 2018 13:50

    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)

  • Admin
    Thomas Hampel commented
    July 17, 2018 02:26

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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 17, 2018 06:49

    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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 17, 2018 08:48

    More than 256 items displayed in a document

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 18, 2018 11:50

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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 18, 2018 16:50

    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.
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 19, 2018 12:09

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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 6, 2018 15:50

    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.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 24, 2018 12:48

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