Updating Text-Script Only Stacks in Run-Time, Message Path Memory
brahma at hindu.org
Sat Nov 5 22:39:42 CET 2016
right… not the engine…
some IDE gremlin…
open some script only stack that had been put into use earlier,
edit save and the changes are available runtime.
So, yes… something is causing the IDE not to pick up the changes in the open scripts and (re)placing it in the message path.
On 11/5/16, 9:28 AM, "use-livecode on behalf of J. Landman Gay" <use-livecode-bounces at lists.runrev.com on behalf of jacque at hyperactivesw.com> wrote:
>ERGO conclude: editing a script only stack and saving it does *not*
>update the "live" version of that file in memory that is in use by
Actually, I've seen the same thing occasionally in regular stack scripts
too, not just script-only stacks. There's been an issue with window
confusion for some time, but I have never been able to get a reliable
More information about the use-livecode