Do script-only stacks support "chained" behaviors?

[Geoff Canyon]

Heisenbug -- as far as I remember the last twenty minutes, the sequence of
edits was:

1. Answer commands die without warning
2. Wrap the problematic answer commands in a try...catch structure.
3. Run the command; get no error from the try, and the command runs all the
way through.
4. Comment out the try...catch structure, leaving the answer commands in
place.
5. Run the command; no errors, everything works fine.

So...something changed, obviously, but I have no idea what. Testing now...

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

> Double-grrr. I put the warning dialogs in the menuPick handler instead of
> the conversion handler, and it works fine. That's *not* where the warnings
> should be, since it means that it's possible to call the conversion handler
> and receive no warnings. I'm testing further. Once I'm comfortable enough
> to try it on (a copy of) Navigator itself, I'll post an update.
>
> gc
>
> On Sun, Jan 21, 2018 at 10:22 PM, Geoff Canyon <gcanyon at gmail.com> wrote:
>
>> 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 :-(
>>
>