Bugs for both issues filed as *Bug 14323* <http://quality.runrev.com/show_bug.cgi?id=14323> - Palette stack does not open unless in debugger
*Bug 14324* <http://quality.runrev.com/show_bug.cgi?id=14324> - Local variable destroyed in attempt to open palette This is repeatable in 5.5 and 7.0.1 (and I think 6.7, but I've lost several hours over this already). On Thu, Jan 1, 2015 at 9:26 AM, Dr. Hawkins <[email protected]> wrote: > > On Wed, Dec 31, 2014 at 10:12 AM, Dr. Hawkins <[email protected]> wrote: > >> But what I'm losing *is* a variable! The selection manipulations have >> been completely removed in favor of a handler that does things on >> textChanged. The problem is that opening a stack is resetting a local >> variable. >> > > I have also tried putting the script-local variable into a handler local > variable, and the script-local still gets reset on the palette command. > > My work-around is to put the script-local into a handler variable, open > the palette, and put it back--but it is unacceptable to need to do this in > a commercial project! > > I have come to the conclusion that either > a) using the palette command is somehow causing a recompile of the script, > wiping out the script-local variables, or > b) the description of the permanence of script-local variables in the > dictionary is wrong. > > There is also, of course, > c) some other psychotic behavior somewhere is maliciously removing > variables. > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
