Hello Mark,
thanks for the quick answer.
All mouse actions work well in the MIAW which tells me that the window has
the focus. The keyDown event I mainly want to trap and stop from passing on
to the input in my editable fields is the RETURN key, this key is almost
always trapped in the event handler, but passed on to the field, despite of
a stopEvent handler that is actually executed.
Other keys like the PAGE UP and PAGE DOWN or the TAB keys are sometimes
trapped (mainly when I start playing the MIAW for the first time), but as I
switch between the stage and the MIAW, sometimes it gets lost, although the
mouse is always working in the MIAW.
I would greatly appreciate it, if anybody had another idea of how to deal
with this.
Thank you and have a nice weekend!
Michael von Aichberger
> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im
> Auftrag von Mark A. Boyd
> Gesendet am: Samstag, 10. Februar 2001 19:12
> An: [EMAIL PROTECTED]
> Betreff: Re: <lingo-l> primary event handler in MIAWs
>
> At 05:34 2/10/2001, [EMAIL PROTECTED] wrote:
>
> >Hello List!
> >
> >I am working on an application that runs as a scripting Xtra (= MIAW) and
> >helps editing another Director movie on the stage.
> >
> >The MIAW has to process keydown events but when the application
> is running
> >as an Xtra, the keydown events are not always intercepted by the primary
> >event handler. Sometimes they are, sometimes the primary event handler
> >ALTHOUGH BEING EXECUTED just doesn't get the events. Moreover I am using
> >stopEvent commands to prevent the RETURN key from spoiling the
> entries in a
> >one line editable text field. They also do not work reliably.
> Sometimes they
> >do, sometimes they do not. And I cannot see any system in this behavior.
> >
> >Up to now I thought that regardless of any other code in any
> other script,
> >the keydown event should always be intercepted by the keydownscript,
> >shouldn't it?
>
> I haven't tried to trap keyDown events in MIAW helpers, but I do
> know that
> the Director authoring environment will always trap certain keys
> before any
> script does. Escape comes to mind here. Still, any pattern as to whether
> the window has the focus?
>
>
> --
> Mark A. Boyd
> Keep-On-Learnin' :)
>
[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!]
