Behaviors and the message path

[J. Landman Gay]

On 12/9/16 4:47 PM, mwieder wrote:
> But at any rate, I believe conflating "extending" a script with
> "concatenation" is the wrong way to think about behaviors.

I think of them as private backscripts, available only the object to 
which they are attached. If the behavior doesn't catch a messages, the 
message continues on to the next object after the backscript's owner.

One thing that surprised me recently was a behavior attached to a shared 
background field. A mouseUp message activated when I didn't expect it 
to. I finally realized that because the behavior was attached to a 
background field, it was being triggered after the card controls. I set 
the field's backgroundBehavior to false (but left the shared property 
true) and the unexpected responses stopped because the field was now a 
card object.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com