LiveCode Forums.

On several occasions while debugging
I've found Rev indicating an error on a line
other than the current one.

Wonder if Rev "optimizes" code as some
other compilers do.

Haven't seen it mentioned anywhere.

Perhaps just a bug?

It sounds like a bug in the script editor. I understand that the beta currently being tested contains a new script editor, so maybe this defect will be corrected in the next few months.

Since I upgraded to 2.9 there's been an
annoying bug in the script editor.

Some changes to the script don't activate
the "Apply" button so I have to press the
"Return" key to insert a new line (which still
doesn't activate the "Apply" button) then
press "Delete" to remove it. That finally
activates the "Apply" button.

It's a real nuisance and has let to loss
of come changes. Wonder has anyone else
had the same problem.

Hope it gets fixed in 3.0.

Hi BJB,

Much more the opposite for me. In 2.8.1 and earlier, the script editor would always have the Apply button activated, even of nothing had been changed. I'm glad they sorted that out.

Can you give an example of when the Apply button should be active but isn't?

Best,

Mark

Mark

It seems to be random so I don't know when
it's going to happen - which make it
difficult (impossible?) to replicate.

But I'll try to catch an example anyway.

Edit:

Had this line...

put max(arrNumbers[]) into field "fldMax"

and when I deleted the "[]" the "Apply" button didn't
activate.

But in the code for the "max" button it did activate.

It's a bug. The 3.0 betas do this right, but the earlier script editors have a problem with this. I think what you're running into with this example is that you're working with an invalid syntax - deleting the "[]" doesn't trigger the "Apply" button in the 2.9 editor but does in 3.0. But changing "max" to "mx" does enable the "Apply" button" - possibly the script editor looks at the change to see if the doc links need updating and only then enables the button. The good news is that the fix is in the 3.0 script editor, so help is on the way.

I realize I was changing invalid code
but who doesn't have to do that now and
then?

I assumed that the "Apply" button would
be activate by the usual "ischanged" sort of
trigger.

Apparently not.

rotfl. It's probably worth reporting as a bug, although I don't know whether there will be a 2.9 point release or not.