LiveCode Forums.

Further to my previous post regarding
the editor not always activating the
"Apply" button and thereby losing code
I've recently had strange things going
on when trying to debug.

On a number of occasions recently
the editor has ignored break points!
This is a nuisance, to say the least.

And even worse - on another occasion
execution stopped at a line at which I
had previously had a break point but
had removed it.

On another occasion the line highlight
move back and forth between two
lines of code (neither of which were in
a loop) and refused to move on.

Feel I've just about had enough of
paying for something which seems to
never be right. Can't believe that it's a
difficult proposition to get this rather
unsophisticated debugger working.

Anyone else had these problems?

Is there relief in sight?

The GLX2 Script Editor includes a new debugger, and I've found it to work better in many situations than the default Rev debugger (however, there are still some situations where the GLX debugger fails, but the default debugger would work).

There is hope on the horizon. Rev 3 has a new script editor and debugger. It is probably only a month or two before R3 is released.

If you can't wait, you could always sign up for the beta program and see if the new debugger satisfies.

Try the "Clear All Breakpoints" menuItem under the Development menu. Stack breakpoints using the IDE's debugger are stored in a custom property and don't always get cleared out when you expect them to be. In addition, editing scripts while there are active breakpoints has always been a bit of a problem.

And I've seen the problem of the highlight not really showing the line of code being executed, but only on scripts that have been saved but not properly compiled first. Could that be what's going on?

I don't know what's going on with the
editor.

It was OK until recently but these problems
are just about making Rev useless.

The last nasty little trick was the disappearing
field -- had to replace it several times. There
was nothing in my code that could have affected
it. Seems to be OK for the present. Fingers
crossed!