ANN: glx2 script editor 4.0

Bob Sneidar bobsneidar at
Mon Apr 6 16:00:43 EDT 2020

Normally I wouldn’t, but in the past for one reason or another I turned off GLX2 to get to the script editor, and somewhere in the process of turning it off and on, a lot of new coding disappeared. That was long ago though, and I may not even be looking at the same problem. It seems that once the stack is saved, everything is in sync.

One other thing, when I enable GLX2, it’s menu becomes the system menu, even if the pointer tool is selected. Is this the desired behavior? No worries if it is. I’ll probably end up living in GLX2 from now on.

Bob S

On Apr 6, 2020, at 12:43 PM, Mark Wieder via use-livecode <use-livecode at<mailto:use-livecode at>> wrote:

On 4/6/20 12:36 PM, Bob Sneidar via use-livecode wrote:
This may be fixed in 4.0.1. I’ll check.
OK I verified that if I make a change in GLX2, then switch to the Native SE, I see the change. If however I make a change in the Native SE, then switch to GLX2, it does NOT reflect the change.
If however I SAVE the stack, THEN GLX2 sees the code change. It must be that GLX2 is maintaining it’s own in memory version of the code, and the switching is not synching in one of the directions. This is likely where the code loss seemed to happen, but seeing this I do not think there was actual code loss.
Maybe a preference to save stack on compile?

So... I'm confused... you want to change the builtin script editor to save after compiling so that it's compatible with the glx2 editor?

Mark Wieder
ahsoftware at<mailto:ahsoftware at>

More information about the use-livecode mailing list