Script Only Stack Architecture

[Sannyasin Brahmanathaswami]

Small addendum, now that I'm actually using them. Today, though I had added them as stack files, my three external stack file behaviors were still not in the message path.

But, now, having added them it the stack files.. you can open them without declaring a path.  


command initializeInterface
set the defaultstack to "SivaSiva"
open stack "generic-mobile-functions_behavior"
open stack "siva_fields_behavior
open stack "siva_portal-links_behavior"


Now they a) appear in the behaviors area to be chosen and applied b) work... 

STILL MYSTERIOUS		

Not clear to me yet exactly when and how you can trigger a save of an external script only stack.

Once you get the hang of this, the new edit script button in the behaviors for your object is going to be your go to button.. edit the exteral script apply.. let's say you have done extensive changes in to that script only stack behavior.

At that moment, how do you save it? When I save the main stack, the Modal feedback does not show the external stacks being saved... on the main stack and 1 binary substack.



On April 1, 2016 at 4:34:56 AM, Ali Lloyd (ali.lloyd at livecode.com(mailto:ali.lloyd at livecode.com)) 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.