hair-pulling frustration

[J. Landman Gay]

On 11/11/2014, 7:24 PM, Richard Gaskin wrote:
> The second one ('98) was one that could benefit from others here who've
> used the debugger more than I have (Jacque, that means you <g>).  I'm
> not sure if it's a bug or merely needs more explanation in the docs.

For reference: http://quality.runrev.com/show_bug.cgi?id=13998

I added a comment there. It is quite possible (and convenient!) to add a 
breakpoint while debugging, I do it all the time. But I have never 
right-clicked, I always just left-click normally on a line number and it 
works. I just tested it again in 7.0.1 rc 1 and it still works here.

The next bug (13999) mentions a popup that should appear when 
right-clicking a line number. I don't see one in 6.x either, and I'm not 
sure I remember ever seeing it, though it vaguely rings a bell. That 
said, right-clicking on an existing and active breakpoint *does* put up 
the expected popup, the one that gives you debugging options. So I don't 
see any problems here.

I don't know if the removal of the line-number popup was intentional or 
even if I'm remembering it correctly. I may be thinking of the popup 
that appears in the Breakpoints pane when you right-click. That one 
still works in 7.0.

The last bug (13999) mentions a greyed-out breakpoint and a lack of 
responsiveness in the script editor. A breakpoint will be grey if its 
script has been edited but not recompiled yet. Since saving a stack will 
also save any uncompiled scripts, the grey breakpoint and a confused 
editor will persist across relaunches.

An unresponsive IDE was mentioned. The editor and the IDE can both 
become "frozen" if you are debugging and you try to do something else 
without exiting debug mode. Not only can you not type into the editor, 
which is to be expected, but most of your stack and even the IDE won't 
respond either (though the message box still works, and the app 
browser.) Almost everything else just stops and you are in a state of 
suspension while the engine waits for debugging to finish. The solution 
is to hit the blue square to stop debugging, or to hit the Run button to 
execute the rest of the handler, and everything picks up again. I've 
never seen the IDE freeze up outside of that situation.

We used to get questions in the support queue about that. People didn't 
realize they were still in debug mode.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com