Clicking the titlebar of the main window, then back to the spawned window
before typing (which should generate Event.ACTIVATE) does not help.
But here's something else that makes no sense. I compiled FocusManager.as from
the Flex 4.13.0 SDK into my app so I could put some trace statements in it. And
without changing anything, that fixed the problem. So I'm not going to argue
with success. I'll just add it to my build, and keep an eye out for other
problems that might arise because of it.
But is it possible that the FocusManager class that's compiled into the 4.13.0
library SWC was not compiled from that source file? I'm quite sure I'm
compiling with the 4.13.0 SDK's mxmlc.bat.
From: Alex Harui <[email protected]>
To: "[email protected]" <[email protected]>; Dave Glasser
<[email protected]>
Sent: Friday, August 21, 2015 6:40 PM
Subject: [BASE64] Re: [BASE64] Re: Odd tab/focus behavior
It could be that that particular AIR window isn’t activated or the
FocusManager doesn’t think it is activated. There are Event.ACTIVATE and
Event.DEACTIVATE that go to each window and FocusManager is listening to
those events.
-Alex
On 8/21/15, 3:12 PM, "Dave Glasser" <[email protected]> wrote:
>It's a desktop AIR app, Alex. It's in a spark.components.Window spawned
>off the main application window, opened with .open(true). And if I click
>the native window's titlebar before I type, it's no help either.
>
> From: Alex Harui <[email protected]>
> To: "[email protected]" <[email protected]>; Dave Glasser
><[email protected]>
> Sent: Friday, August 21, 2015 5:23 PM
> Subject: [BASE64] Re: Odd tab/focus behavior
>
>Sounds like the browser hasn’t activated the SWF? Maybe SWFObject no
>longer works properly on certain browsers?
>
>-Alex
>
>
>
>On 8/21/15, 2:10 PM, "Dave Glasser" <[email protected]> wrote:
>
>>I'm using Flex 4.13.0, on the AIR 14.something platform. I have a login
>>dialog, that has username/password fields (both mx.controls.TextInput)
>>that are in a VBox in a Panel that was popped up by the PopUpManager.
>>Inside a handler for its creationComplete event, I am focusing the
>>username field like this:
>>usernameField.setFocus();
>>and I've also tried
>>
>>focusManager.setFocus(usernameField);
>>When the dialog first appears, the cursor is blinking inside the username
>>field and it has the focus rectangle, as you'd expect. When I type in a
>>username, the letters appear in the field as expected.
>>The problem is that the first time I hit the tab key, nothing happens.
>>Maybe the cursor inside the field flickers but that's it. And if I hit
>>the tab key a second time, it behaves as expected, with the focus moving
>>to the password field.
>>
>>If, before I hit the tab key the first time, I click inside the text
>>field with the mouse, then the first tab keystroke shifts the focus as
>>expected.
>>Has anyone encountered this before?
>>
>
>
>
>
