Thanks Jakob and Kerry. I found the problem on my own. Clicking on a button inside a MIAW was initiating the process which created the timeout. So it was being added to the timeout list of the MIAW rather than the stage. Telling the stage fixed it.
I used to keep a reference to the timeout object for earlier projects, but ran into problems forgetting it. I'd have to perform two steps, one to forget it from the timeout list and the second to set the internal property reference to void. Pranav Negandhi Software Engineering Learnet India Limited, Mumbai. Phone: 91-22-56768120 http://www.learnetindia.com Does anybody remember laughter? -- Robert Plant, The Song Remains the Same. <snip> >on Destroy me > callAncestor(#Destroy, me) > timeOut("StrategyMove" & me._ID).forget() >end Destroy me Maybe you should keep a ref to the timeout in your object, rather than relying on lookups. <snip> [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!]
