> i could be confused. before the timeout objects i used to use a custom
> object that did the same think, and i know we could do it in ours.
> should be easy enough to test though...
I already tested it a while ago, and you know what does get passed? The name
of the timeOut itself. Odd, isn't it?
on beginSprite me
timeOut ("TimeOutName").new(1000, #catchTimeOut, me, "param1", "param2",
"param3")
end
on catchTimeOut me
repeat with i = 1 to the paramCount
put param(i)
end repeat
end
Message window output:
-- <offspring "" 4 125e0a4>
-- timeOut("TimeOutName")
-- <offspring "" 4 125e0a4>
-- timeOut("TimeOutName")
-- <offspring "" 4 125e0a4>
-- timeOut("TimeOutName")
-- <offspring "" 4 125e0a4>
-- timeOut("TimeOutName")
So, the first parameter the handler sees is "me" (hence <offspring "" 4
125e0a4>), the second parameter it sees is timeOut("TimeOutName") - the
surprising bit, and that's where it stops, which means that all the other
parameters are ignored. It doesn't return an error though, which is also
surprising.
Karina
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]
