Re: "after after" for behaviors?

Set a global, then have an idle handler in a back script check the global. Have the idle handler check the contents of the global. If empty pass idle, otherwise and accordingly, then reset the global to empty when done. Bob S On Jul 23, 2016, at 11:05 , Dr. Hawkins

Re: "after after" for behaviors?

It's hard to tell from your description how you want the final script to be triggered. It sounds like there are multiple handlers that can initiate the final script, and because of that I imagine you DO need to add a trigger command to each handler. I was going mention the possibility chained

Re: "after after" for behaviors?

Your "least ugly" idea is the only one I can think of too. Send the command at the end of the sequence. On 7/29/2016 3:13 PM, Dr. Hawkins wrote: *bump* any ideas, anyone? On Sat, Jul 23, 2016 at 11:05 AM, Dr. Hawkins wrote: I am trying to implement a generalized

Re: "after after" for behaviors?

*bump* any ideas, anyone? On Sat, Jul 23, 2016 at 11:05 AM, Dr. Hawkins wrote: > > I am trying to implement a generalized behavior that triggers after the > entire execution path, rather than after the immediate script, but before > the next script in the path. > > Actually,

"after after" for behaviors?

I am trying to implement a generalized behavior that triggers after the entire execution path, rather than after the immediate script, but before the next script in the path. Actually, having control return to a handler after "pass someHandler" would also solve my issues. A control might be