Re: FW: Using NextFocusableComponent attribute
Frank Meissner <[email protected]>
| Newsgroups | gmane.comp.embedded.carlsbad-cubes |
|---|---|
| Message-ID | <[email protected]> |
Hello Kämäräinen, another thought occured to me. The usual FocusTraversalPolicy of a container (I'm certain you have) is IMHO ContainerOrderFocusTraversalPolicy. This is quite useful in the ususal circumstances. That means, you have unusual ones ;) Perhaps you re-arrange the order your buttons occur in the XML? E.g. if you have GridBagLayout you can do a lot by using GridBagConstraints.gridx and the like. Or, if you *are* using these attributes right now, just change the order of the button-tags. Frank Kämäräinen, Teemu wrote: > This is a repost because I have got no reply for my question. > > -----Original Message----- > From: Kämäräinen, Teemu > Sent: 1. huhtikuuta 2004 11:01 > To: '[email protected]' > Subject: Using NextFocusableComponent attribute > > > Hi all! > > How should the NextFocusableComponent attribute be used? > I mean, in which form should a Component-typed attribute > be typed into the XML? > > Let's except e.g. we have three buttons, named "firstbutton", > "secondbutton" and "thirdbutton". By default the Tab-key > transfers the focus from "firstbutton" to "secondbutton", > but we would like the focus to move from "firstbutton" to > "thirdbutton". What kind of NextFocusableComponent attribute > definition should be added to the button tag defining > "firstbutton"? > > Thanks in advance. > > > --Teemu > > -- > TTM-Tieto Oy > Teemu Kämäräinen > > GSM: +358 44 700 3227 > E-mail: [email protected] > > > ------------------------------------------------------------------------ > > _______________________________________________ > Forum mailing list > [email protected] > http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com