I appear to be having a problem with the script debugger that I can’t seem to resolve. The debugger will work fine for some of my LotusScript agents. However, when I attempt to debug other LotusScript agents, the debugger window appears but there is no code in window. The only options I have available are to stop the debugger and close the debugger. I can’t quite seem to figure out a pattern to this. Has anyone encountered this yet? I’ve tried wiping out Notes and reinstalling, but still no luck.
I ran into this issue, as well (which is how I came across your post).
In my case, I had an agent that uses a script library. Upon agent launch, the debugger would arrive at the “empty” debug window that had no options other than to Close, or Stop. I noticed that if all the library code were incorporated into my agent, the debugger would start normally. This, however, wasn’t really an option for me because there are multiple agents that will share the set of functions in the library, and I did not want to have to incorporate them all directly into the body of each agent.
After about two weeks of stalled progress, during which time we reinstalled Notes, then Windows, then dropped back from XP to Win2k, all without luck, something occurred to me: I had been saying, all along, that it seemed as if the debugger was getting lost at the ‘intersection’ of the library and the agent; and, as that basically corresponded to the ‘Initialize’ event of the library, and as there was, indeed, code in the Initialize event, I might try moving all the code of the Initialize into a kludge function, then I’d call that function from the body of my agent after Notes had successfully ‘touched’ the library and returned me, in the debugger, to the Initialize of my agent. And, sure enough! It worked!
This problem, for whatever reason, did not manifest itself in Notes 6.0 (on top of Win2k).
It’s still not solved. We have had this problem appearing with several design elements (forms, database script,…), but always with one common denominator: 1 or even several script libraries !
I’m having a similar issue trying to debug LS in the QuerySave event on one of my forms…how irritating!!
The form usually gets created by using an action button, but I’ve found that if I create the document using the ‘Create’ menu option then the debugger will step through the QuerySave event when the doc is saved…weird, but it seems to work for me…
Thanks for the hint, but that was not the issue. The code window was plainly visible–just no code in it. I discovered some similarities between agents that can be debugged and agents that can’t. It appears that using several script libraries causes the debugger to hang on my machine. When I run the debugger on ‘simple’ lotusscript agents, I don’t have a problem. But running it on more complex agents that use multiple script libraries appears to cause a problem.
