Something’s very strange. I can switch the debugger from active to inactive. But the buttons to the left of the switch are always greyed out.
Yes, there’s a method ready to be tested.
Any ideas?
Make sure you’re not in designer
jaleman:
Make sure you’re not in designer
By going out of designer mode the green triangle is revealed. But the rest of the icons are greyed. I’ve inserted break points.
Correct.
Until you start running the method (by pressing the green triangle) the other buttons are disabled (you can’t step through a method if it ain’t running)
jaleman:
Correct.
Until you start running the method (by pressing the green triangle) the other buttons are disabled (you can’t step through a method if it ain’t running)
I’m being particularly dense this morning (as usual). By clicking the run icon script runs right past the break points (large orange dots) right through to the end.
Clicking the Variables, Debug, Watch, Evaluate or Output tabs before running has no effect.
If the breakpoint dots are orange the debugger is not enabled, only when the are red they are active.
Rafi CV Latest.pdf (72.7 KB)
Jan Blok:
If the breakpoint dots are orange the debugger is not enabled, only when the are red they are active.
Thanks.
Supplemental debugger question. In both the Output and Debug tabs there’s a long list of actions from previous runs. How does one clear them after they’ve served their purpose?
I notice it’s imperative to put a breakpoint right at the beginning of a script. Otherwise one doesn’t get access to the Step Into, Over, Out controls. Puzzling why the debugger was set up that way.
The Enable/Disable Entry Break feature is puzzling. There’s no visual feedback on whether enabled or not, nor have I discovered any difference in any action. Don’t understand the utility of this feature.
A tutorial for the debugger would be useful if someone knows of one.
In both the Output and Debug tabs there’s a long list of actions from previous runs. How does one clear them after they’ve served their purpose?
Right moues button → clear
I notice it’s imperative to put a breakpoint right at the beginning of a script. Otherwise one doesn’t get access to the Step Into, Over, Out controls. Puzzling why the debugger was set up that way.
The Enable/Disable Entry Break feature is puzzling. There’s no visual feedback on whether enabled or not, nor have I discovered any difference in any action. Don’t understand the utility of this feature.
If you enable entry breaks the debugger will always allow you to walk through every step WITHOUT you having to set a breakpoint. If you disable that the debugger will only stop if you set a breakpoint.