Do script-only stacks support "chained" behaviors?

[Geoff Canyon]

Also, status update: grr. I'm finding that the answer dialog I'm using to
warn the user that the script conversion process is dangerous and to work
on a backup is causing my script to die, no warning, and no error message.
The exact same script *not* running in Navigator works fine. Answer dialogs
in other Navigator handlers also work fine. I have zero idea why this might
be. Other than this I'd be testing away and releasing :-(

On Sun, Jan 21, 2018 at 10:19 PM, Geoff Canyon <gcanyon at gmail.com> wrote:

> It occurs to me that this isn't as much of a problem as I thought -- any
> button being converted to a stack is highly unlikely to have an openstack
> handler already in it, and therefore it would be safe to add one and
> include setting the behavior of the script-only stack to the appropriate
> stack up the chain. If there were already an openstack handler in the
> chain, then the conversion process could stop at that point, or perhaps log
> the error to the user. Unless I'm missing something?
>
> On Sat, Jan 20, 2018 at 5:15 PM, Trevor DeVore via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> On Sat, Jan 20, 2018 at 6:43 PM Geoff Canyon <gcanyon at gmail.com> wrote:
>>
>> > Well that's too bad for anyone who's currently using chained behaviors
>> and
>> > wants to use source control (i.e. convert to script-only stacks).
>> >
>> Yes it is.
>>
>> For now I just set the chained behaviors for any script only stacks that
>> require them when the app starts up. Not ideal, but worth it in order to
>> manage the scripts with source control.
>>
>> Trevor DeVore
>> ScreenSteps
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>