Lotus Script Debugging - VERY POOR

HCL Domino Domino Forum
1

I am trying to debug some form events in a form that is opened by:

Call workspace.editdocument(true, doc)

The postopen and querysave events have the code that I wish to debug.

I turn the debugger on and click the button that runs the editdocument code.

The postopen and querysave events do get triggered but, they are not picked up in the debugger. This is very poor, Lotus.

Anyone else had this problem? Is it a bug?

It can’t possibly be designed tyo work that way!!!

2

Subject: Lotus Script Debugging - VERY POOR

Try putting the “Stop” statement in your code. This causes the debugger to stop at that point as though it were a defined breakpoint.

3

Subject: RE: Lotus Script Debugging - VERY POOR

This would work if the Debugger had a handle on the events, but it doesn’t. So, this way won’t work for me.

Thanks anyway though :slight_smile:

4

Subject: Lotus Script Debugging - VERY POOR

At least you are not getting an NSD screen popping up and closing Notes every time you enable the debugger.

I have talked with Lotus Tech Support about this and cannot even use the debugger most of the time.

It is annoying trying to debug code without having the use of a debugger.

5

Subject: Lotus Script Debugging - VERY POOR

I don’t think it’s a bug. I think the debugger probably works on a per process (or thread) basis. You’ve attached the debugger to a process by turning it on for the code that’s calling the “EditDocument” method. But when you call this method, I suspect the resulting form events execute in a new (and separate) process/thread to which the debugger is NOT attached. I’m not saying that it wouldn’t be a “nice-to-have” feature for the debugger.

If there’s a reason that prevents you from debugging the form events directly from the form, I’d suggest peppering your form events with “Print” statements and/or messageboxes to check variable values & states. That’s the way Java programmers had to do it for years until some of the nicer IDEs were released! :slight_smile:

dgg

6

Subject: Lotus Script Debugging - VERY POOR

Hi Rob,

I don’t know what IBM/Lotus has done with the script debugger in Version 6, but its indeed very poor ! In Version 5 it had memory leaks casue after a while of use one had to restart the client, but it was useable.

Now I have loads of problems with it. Some errors are displayed in a messagebox, but are absolutly not debuggable. And as the errormessage are unspecific, you have a pretty bad job in finding out, whats wrong.

Another problem is that some errors mcan occur while running in non-debug (normal) mode and in debug mode . . . no errors . . . and so on.

Guess we have to live with it, but we have frozen further complex script development. We only use what works :frowning:

Joe