PDA

Click to See Complete Forum and Search --> : tabIndex useless b/c of Components?!



Synic
05-14-2004, 08:39 PM
Been having a lot of problems with tab order using tabIndex on different form elements.

What I have discovered is that if I use an MXPro component on the stage with my other form input fields, that tabIndex on all other movieclips simply stops working.

Has anyone experienced this?

Here is a link to an example:
http://64.207.177.164/test.htm

and two links to the .fla's in the example-
The one that works -(no components):
http://64.207.177.164/flash/test_noMM.fla

..and the one that doesnt:
http://64.207.177.164/flash/test_MM.fla

miakazi
01-04-2006, 06:20 PM
we're having the same problem. Does anyone have a solution?
miakazi

g-s-b
02-04-2006, 05:32 PM
I can't resolve this one either. Others are posting the same problem in other forums but I've yet to see a response.

g-s-b
02-05-2006, 12:23 PM
OK, here's some progress. I found that just having a component in the library, on stage or not, disables the tab index on the other symbols. With that in mind, I tried putting a scroll component in another swf, then adding it to the mix with loadMovie. It restores the tab index of the button symbols but does some funky things with the loaded movie. Right now, I'm bypassing the movie with the component by assigning a tab index to the symbols only. It's not perfect, but it's better than doing without tab indexing all together.

I'll keep checking back to see if anyone comes up with a better solution or builds on this one.

Dene
08-21-2006, 03:51 PM
This will disable the FocusManager:

_level0.focusManager.enabled = false;

That line needs to be called AFTER the first frame to ensure the focusmanager has already been set up.