J. Landman Gay wrote:
On 3/31/2016 1:42 PM, Sannyasin Brahmanathaswami wrote:
ergo: merely opening a script-only stack that is applied as a
behavior to a control (not global in scope) does*not* place into the
msg path.
By the time a preOpenStack handler executes, the engine has already
loaded the stack into RAM and set up the behaviors. You need to load the
behaviors before your mainstack even launches. That's why Richard said
it may require a launcher app that opens the behaviors first and then
opens the mainstack.
To avoid that, the only method available would be the stackfiles lists.
The engine apparently checks those first before setting up the behavior
linkages.
As usual, Jacque manages to explain it better if far fewer words. :)
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
