Script Editor disassociates - a lossy LC IDE bug

[hh]

I reported a bug (#18688, Oct 26 - 2016) that is still there in 9.5.0
on Mac 10.15.1. It partially overlaps with your description:

[1] Saving a stack while the script editor is open with an unsaved
script doesn't save the script.
[2] Quitting LC without closing (saved) stack window or SE doesn't
save unsaved scripts.


> Curry K. wrote:
> Wondering if this bug has already been reported?
> 
> I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window 
> seems to disassociate from the object being edited. Thus after this bug 
> is triggered, any typed script changes may not really be applied and 
> saved, although they are shown as applied. Next LC session, those 
> changes are gone; the stack code is still as it was prior to the bug 
> being triggered and prior to editing the script.
> 
> An alternate form is that the script changes actually are applied, but 
> in a bad way: first the script disassociates completely and is empty, 
> then the empty script is saved, overwriting the previous script. Nice! 
> (I think this is my favorite variation; if we're going to cause loss of 
> work/code, might as well do it boldly and not beat around the bush.)
> 
> I suspect this happens more on Mac than Windows, but since I don't have 
> a recipe, not sure. I've seen this happen to other people rather than on 
> my own machine. On LC 905 for sure, and probably on 950 also.
> 
> If Script Editor disassociation does happen, I advise immediate but 
> careful no-save quit or force quit, and pray that you're already in the 
> habit of backing up beforehand. Copy and paste the current script text 
> to an external text editor if necessary. Of course this particular bug 
> just might be able to defeat the safety of stack backups too in some 
> situations, but hey, that's why it's an extra-fabulous bug!
> 
> So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit 
> work-lossy. That could turn off both new and old users if they are the 
> humor-deficient type to frown on losing some work. But shucks, ain't no 
> thang! Only features features features (and new side projects) matter! 
> Glad we all agree on that.
> 
> Any reports or recipes on this issue? I'll post a report if there is 
> none. Thanks....