Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread Bob Sneidar
When I worked on Radars, many technicians were convinced there were electronic gremlins, because the rate at which the equipment suffered a failure within days before a missile test was uncanny. I am not superstitious, but by the time I was discharged, I was not ruling out the possibility. Bob

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread Peter Haworth
On Thu, Mar 20, 2014 at 8:54 AM, Richard Gaskin wrote: > For example, if you have a mainstack which is an executable and contains > objects that use behaviors, and a separate library stackfile which contains > the behavior buttons, it will always fail because that mainstack is opened > before the

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread Devin Asay
On Mar 20, 2014, at 9:54 AM, Richard Gaskin wrote: > Devin Asay wrote: > > So it appears that each time I launch the project I have to reassign > > the behavior to the buttons. This only seems to happen for behaviors > > stored in library stacks. I have seen a similar problem with objects > >

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread J. Landman Gay
On 3/20/14, 10:54 AM, Richard Gaskin wrote: To simplify this occasional necessity, I had hoped the team would have implemented a command they once talked about in the early days of behaviors but never quite got around to: "resolve behaviors", which would trigger the same resolution mechanism that

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread J. Landman Gay
On 3/20/14, 10:09 AM, Devin Asay wrote: So it appears that each time I launch the project I have to reassign the behavior to the buttons. This only seems to happen for behaviors stored in library stacks. I have seen a similar problem with objects that were assigned a background pattern stored in

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread Richard Gaskin
Devin Asay wrote: > Later I discovered that *someone* (I blame the code kabouters*) had > gone in and assigned icon states to the buttons using the behaviors, > rendering the BEFORE and AFTER handlers redundant. I like "kabouters". I have a friend who refers to unexpected behavior in software

Re: before vs on in behavior scripts - red herring alert!

2014-03-20 Thread Devin Asay
On Mar 18, 2014, at 5:33 PM, Devin Asay wrote: > All, > > If a button has a behavior attached to it, and the behavior script has a > 'before mouseUp' handler, can the behavior script also have a 'on mouseUp' > handler? > > I could swear the answer was yes; I thought I had done that before, b