You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@flex.apache.org by mark goldin <ma...@gmail.com> on 2014/01/06 18:45:03 UTC

FlexEvent.FOCUS_IN

Is there a way to find out what triggered that event? Was it a mouse click
or a tabbing in?

Thanks

Re: FlexEvent.FOCUS_IN

Posted by mark goldin <ma...@gmail.com>.

These keys I think will work after the control gets the focus but not
before.


On Mon, Jan 6, 2014 at 12:13 PM, Alex Harui <ah...@adobe.com> wrote:

> It could also be programmatic or happen when the app is re-activated when
> switching back to it from another app.
>
> There are KEY_FOCUS_CHANGE and MOUSE_FOCUS_CHANGE events that might be
> helpful.
>
> On 1/6/14 9:45 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >Is there a way to find out what triggered that event? Was it a mouse click
> >or a tabbing in?
> >
> >Thanks
>
>

Re: FlexEvent.FOCUS_IN

Posted by Alex Harui <ah...@adobe.com>.

It could also be programmatic or happen when the app is re-activated when
switching back to it from another app.

There are KEY_FOCUS_CHANGE and MOUSE_FOCUS_CHANGE events that might be
helpful.

On 1/6/14 9:45 AM, "mark goldin" <ma...@gmail.com> wrote:

>Is there a way to find out what triggered that event? Was it a mouse click
>or a tabbing in?
>
>Thanks

Re: FlexEvent.FOCUS_IN

Posted by Gary Young <fl...@gmail.com>.

just an idea:

remember mouse click and keyboard tab key event and timing from stage( they
all popup to root stage ), and then you can tell from focusIn handle by see
which is the last possible one.

-Gary

On Mon, Jan 6, 2014 at 12:45 PM, mark goldin <ma...@gmail.com> wrote:

> Is there a way to find out what triggered that event? Was it a mouse click
> or a tabbing in?
>
> Thanks
>