script scope variables inexplicably becoming unset

Dr. Hawkins dochawk at gmail.com
Thu Jan 1 12:26:19 EST 2015


On Wed, Dec 31, 2014 at 10:12 AM, Dr. Hawkins <dochawk at gmail.com> 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



More information about the use-livecode mailing list