Here’s the problem:
My goal is to debug a script behind a hotspot action.
I activate the LotusScript Debugger and open a database. I automatically enter the open scripts in debug mode. Everything works fine. Now, I enter a document created with the form containing the hotspot I want to debug. The debugger automatically switch to debug mode for the postopen script. Everything works fine again. Then I click the hotspot link. The “/$”/ debugger doesn’t fire!! I’ve tried to copy paste the link in the form because it was in a subform, but it does nothing. I’ve tried with the Designer client closed, nothing.
This annoying problem exists since R4 I think. Why is the stupid debugger doesn’t fire on some scripts?? I’m using this bugged features only when I REALLY REALLY need it because its behavior is so unpredictable. Is there any limitations or any explanations of the weird behavior of this ‘debugger’?? I’m using R7 and I’m having the same problem I had in R4!!!
Hey guys! I can understand bugs like the bugged toolbars and some red-screen-of-death, but the debugger is an important feature and after so many years it must be rock solid!
Like I said in other topics I’ve started on Notes.net… It’s better thinking about what wrong with the current features instead of creating new ones.
Now I’ll take a deep breath and, again, I’ll debug my script with tons of prints and message boxes…