Skip to main content
December 8, 2011
Question

Flashbuilder 4.6 Mobile Air Projects broke tabbing through TextInput? or am I missing something...

  • December 8, 2011
  • 1 reply
  • 1086 views

(1) Create a project : Flashbuilder 4.6 Mobile Air Project

(2) lay out 5 <s:TextInput> ti1, ti2, ti3, ti4, ti5

(3) compile

(test 1) hit TAB key. it does nothing when testing on the computer

(test 2) hit TAB soft key on a xoom tablet, it does nothing as well.

* shouldn't it be tabbing to the next TextInput?

* Flex 4.51 it works fine

* Flashbuilder 4.6 Desktop Air projects works fine as well

Seems to be a problem ONLY when creating a Flashbuilder 4.6 Mobile Air Project...

i've tried

(1) tabEnabled="true"

(2) tabFocusEnabled="true"

even tried

(3)

// BEGIN CODE

trace(charCode)

if(event.charCode == 9)

{

ti5.setFocus();

}

// END CODE

// charCode == 9 which is the tab key, it fails to change focus.

// when i change to a different charCode, example charCode == 0 which is the shift key, then it seems to set focus fine.

This topic has been closed for replies.

1 reply

December 8, 2011

After spending another day on the issue, I don't think I'm missing something.

// [ TEST CODE ]

<fx:Script>

         <![CDATA[

                  import mx.managers.FocusManager;

                 

                  protected function ti1_keyDownHandler(event:KeyboardEvent):void

         {                      

                     trace(focusManager.getNextFocusManagerComponent())                     

         }

                 

            ]]>

      </fx:Script>

     

      <s:TextInput id="ti1" x="148" y="138" keyDown="ti1_keyDownHandler(event)"/>

      <s:TextInput id="ti2" x="148" y="213" keyDown="ti1_keyDownHandler(event)"/>

      <s:TextInput id="ti3" x="150" y="300" keyDown="ti1_keyDownHandler(event)"/>

      <s:TextInput id="ti4" x="148" y="381" keyDown="ti1_keyDownHandler(event)"/>

// [ RESULT : FAILED in Flash Builder 4.6 Air MOBILE project ]

//stuck on the first component.

test4_0.ApplicationSkin2._ApplicationSkin_Group1.contentGroup.ti1

test4_0.ApplicationSkin2._ApplicationSkin_Group1.contentGroup.ti1

test4_0.ApplicationSkin2._ApplicationSkin_Group1.contentGroup.ti1

test4_0.ApplicationSkin2._ApplicationSkin_Group1.contentGroup.ti1

//[RESULT : WORKS in Flash Builder 4.51 Air MOBILE project and Flash Builder 4.6 Air DESKTOP project ]

//cycling to the next component properly

test0.ViewNavigatorApplicationSkin2.navigator.ViewNavigatorSkin4.contentGroup.testHomeView15.SkinnableContainerSkin16.contentGroup.ti2

test0.ViewNavigatorApplicationSkin2.navigator.ViewNavigatorSkin4.contentGroup.testHomeView15.SkinnableContainerSkin16.contentGroup.ti3

test0.ViewNavigatorApplicationSkin2.navigator.ViewNavigatorSkin4.contentGroup.testHomeView15.SkinnableContainerSkin16.contentGroup.ti4

test0.ViewNavigatorApplicationSkin2.navigator.ViewNavigatorSkin4.contentGroup.testHomeView15.SkinnableContainerSkin16.contentGroup.ti1

// At first I thought it was a TAB issue, but it looks like a focusManager.getNextFocusManagerComponent issue.

chris.campbell
Legend
December 8, 2011

Thanks for the heads up.  Would you mind adding a bug report on this over at bugbase.adobe.com?  Please include your code, a working app if you can, and a link to this thread?  I'd definitely note also that this worked with the previous SDK and is broken with 4.6.0.

Thanks,

Chris

December 8, 2011

K,

submitted a bug and attached code file as a .fxp

https://bugbase.adobe.com/index.cfm?event=bug&id=3064944