Thank you Kerry and Alex for your replies. I was aware of the issues when
using the forget command with MIAWs, couldn't remember if there was any
relation to timeout objects or not.
Along the same lines, if I have placed an instance of an object into a
global variable, does it destroy the object when you zero that global out?
I know there has been discussion on this before, but I just wanted to verify
the proper procedure.
Thanks,
-_Craig
It's not a problem to have the timeOut forget itself, but there's a bug in
Director you need to be aware of. Jakob reported this a while back.
The way you are creating the timeOut, it will never leave memory. You need
to assign it to a variable--any old variable. A local dummy variable that
immediately passes out of scope is ok. E.g.:
disposableVar = timeout("thisTimer").new(1000, #handlerToCall, me)
Of course, if the variable is global or property, or stays in scope, you'll
need to zero it out when you forget the timeOut.
Cordially,
Kerry Thompson
Craig Taylor
Founder/Multimedia Developer
E: [EMAIL PROTECTED]
Renegade Digital Media inc.
T: 705.733.1096 | F: 705.733.0503
C: 416.930.5206
M: 30 Summerset Drive, Barrie, ON, L4N 9L7
www.renegadedigital.com
(digital).video | (interactive).multimedia | (web).solutions
(DVD).authoring | (live_event).media_support
[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
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
