> Hey Mark, > > thanks for keeping glx alive. Is there a changeLog somewhere? Will you see > it if I post issues to the bitbucked site? I would really love being able > to use glx again, however, there is one issue which currently keeps me > from it. If I try to compile an errant script, no error info is given. Do > you have any idea how I can fix that?
There's no changelog for this build other than notes in individual scripts. I'd summarize it by saying this one works slightly better than the previous build. Mostly there's internal code cleanup, things work a bit faster than before, etc. There's still a known issue where if you switch between the chalkboard and alabaster motifs the colors don't propagate correctly immediately until the next time you close and relaunch the editor. I won't be able to look at that until after the conference. Ideally I will see issues posted on bitbucket, we'll have to try it. And I've occasionally run into that thing where there's no error info before. Not consistently enough to have anything to fix, though. And sometimes compiling a second time does highlight the error. I'd love to have a recipe that just failed the same way every time. It's probably on my plate to fix that because it has to do with interaction between the script editor and the debugger. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
