Am 18.05.2005 um 19:20 schrieb Thomas Higgins:
timeout objects have long received these system events and the
behavior described is as intended and by design, this is in no way a bug
(one might argue it's not optimal but as of today it's working completely as
designed and expected [based on that design]).
In an ideal world the events sent to timeout targets, shouldn't get routed down the event hierarchie chain, but instead be sent ONLY to the timeout targets.
if these events would be sent to the timeout targets just like some of us send the events to scriptobjects:
call(#startmovie, [timeOutTarget])
the problem wouldn't occur -> the event would die in < timeOutTarget>, but wouldn't throw and error, if the event has no corresponding event handler in <timeOutTarget>.
while this sounds to be an easy solution, I realize, that I haven't got the knowledge about the inner workings of directors application code and must admit, that it may only SOUND easy, but is in fact much more work to actually implement.
---------------------------
||| ażex
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email lingo-l@penworks.com (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
