And yet another workaround, IMHO cleaner, is to set the editable =
false immediately after setting enabled = false in actionscript.
--- In flexcoders@yahoogroups.com, Brendan Meutzner [EMAIL PROTECTED]
wrote:
Another workaround is to nest the ComboBox in a Canvas container and
then
Another workaround is to nest the ComboBox in a Canvas container and then
enable/disable the Canvas... you can see a tiny bit of disabled coloring
bleeding over the radius of the ComboBox corners, but you've really gotta be
looking.
Brendan
On 20 Mar 2007 11:06:03 -0700, Paul Whitelock [EMAIL
I actually discovered this same issue in my app a few days ago. I also
have several other ComboBoxes (including one right next to the
problematic one) that don't display the i-beam.
After a bit of investigation, it seems that having enabled=false in
the ComboBox's MXML tag (then enabling it at
Thanks Ben, that helped a bit.
I have two ComboBoxes on the Form and each had an enabled=false in
the MXML. However, when I removed the enabled=false from the MXML I
was still getting the i-beam and selectable text.
In my code I'm also programatically changing the enabled state of the
I just discovered why the second ComboBox was not affected -- it's
because I was disabling the ** Form item ** that wraps the ComboBox
and not the ComboBox itself.
I changed my code so that I enable and disable both ComboBoxes by
setting the enabled property for the Form item rather than for the
5 matches
Mail list logo
