Just wanted to tell you that my problem (keyUp handlers in a MIAW not
responding anymore after clicking in that MIAW) is partly solved. I got a
hint from another mailing list, indicating that this strange behaviour is a
known director bug, but that it is in authoring mode only. I checked it out
an
At 07:43 PM 6/23/2001 +0200, you wrote:
>What I need is a text field in a MIAW that executes a keyUp handler no
>matter what the user does with the mouse and no matter what window is
>active.
You may not have your second and third wishes as thjey are unrealistic, but
if your user clicks in an ed
> Only thing I can think of is if the MIAW's text field has focus, even if
the movie is out of focus, Director *might* try to deliver the event there
anyway.
Well, if I can set the focus of a textfield in a movie that hasn't got the
focus, how can I set the focus to that movie via Lingo - the act
Only thing I can think of is if the MIAW's text field has focus, even if
the movie is out of focus, Director *might* try to deliver the event there
anyway.
Generally Director attempts to deliver events first to the sprite, then to
the castmember, the frame, and the movie.
I don't know what
Hi Tab, thanks for answering.
> particularly since B is supposed to launch A, so how
is it that the handlers run in A when you start b?
A is in front of B and the keyboardfocussprite is a sprite in A
(B calls A with this Lingo:
wMain.fileName = A
moveToFront wMain
tell wMain
go t
