That’s good, but you really should create a new set of stacks, copy over your code or rewrite it in the new stack, and see if you can reproduce the same results.
Here, when I palette a stack from a name derived from a script local variable, the variable stays intact. I’m not using your exact setup/variable names, but if I understand what you’re doing, the basic premise works fine. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On Jan 2, 2015, at 12:01 PM, Dr. Hawkins <[email protected]> wrote: > On Wed, Dec 31, 2014 at 2:01 PM, Scott Rossi <[email protected]> wrote: > >> Another useful process is to create a simple set of test stacks and copy >> over your relevant handlers. If you can recreate the problem there, you >> may have found an odd bug, but if not, the problem likely lies elsewhere in >> the code of your original stacks. > > > I've stripped the stacks to almost nothing, and still have the behavior, > reproducibly. There is almost no code left. > > Either there is code around that the debugger won't show yet still > executes, the stack is corrupted in an exotic way, or there is a bug: > both bugs bite without any of my code being executed. > > > -- > 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 _______________________________________________ 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
