That won’t work in my case…the
root of the problem is it’s applying the function(s) to the previous
contents of the textinput field. -Stace From: Stacy, I have had this problem as well L I am sad to say, I
hate the focus manager. Ok that was a little harsh… but none the
less, it has its’ issues. There is a way to set the position of the
caret though (Set the start index of the caret as well as the end, so you can
choose the text you wish to be highlighted). I am going to try to find
that code. In the mean time, you may want to try setFocus in the show
event or childrenCreated event. That may fix your issue. If not,
then the code for setting the caret position may help. I will find that
code and post it. Give me a few… Dustin Mercer From: Tiny problem but it’s still driving
me nuts. I’ve got a viewstack that’s changed based on a users
selection. Each time a container within that stack is viewed an initialization
script is run to populate form elements. At the end of the process I’m
using setFocus to, well, focus on the first textinput field. The problem is the
selection on the textinput field is the length of the previous value for that
field. So if the current value of the textinput is “abc” and the
model changes to “abcdef”…When the setFocus executes
it’s only highlighting from a to c Hope that was clear, ‘tis
late… Thx Stace
|
Title: Loading mxml Components
- RE: [flexcoders] setFocus is evil Stacy Young
- RE: [flexcoders] setFocus is evil Stacy Young
- RE: [flexcoders] setFocus is evil Mercer, Dustin