Thanks for taking the time to explain this Mark. After I thought about it for awhile I expected that this would be your answer and again I’m very pleased with how you’ve implemented the behavior feature.
Tim Bleiler, Ph.D. Instructional Designer, HSIT University at Buffalo > On Dec 12, 2016, at 4:38 AM, Mark Waddingham <m...@livecode.com> wrote: > > On 2016-12-09 19:44, Bleiler, Timothy wrote: >> I still have one question though. Given the part of your answer I >> quoted above, why does the “pass” control structure trigger handlers >> along the behavior chain rather than skipping over them and going to >> the next object in the ownership chain? > > Because it is helpful for it to do so. > > Either 'pass' could act as you say and skip the entire behavior chain; or it > could do as it currently does and pass to the next script in the list of > things which might want to process the message. > > Given the utility of pass in the exisiting message path, it seemed sensible > that it should do the 'similar' thing in the behavior chain. As currently > implemented, it means that you can get a whole list of things to 'do > something' on a particular event; should each one pass (just as you can with > the 'normal' message path). > > Warmest Regards, > > Mark. > > -- > Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > LiveCode: Everyone can create apps > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
