<rant> Yes thats the conclusion that I had reached this morning when working with it. I was just wondering if there was a reason to hide it from codeHinting. I mean they must have put that in there for a reason?
I can't fathom it. Not on this work iteration but on one serveral weeks back I lost a lot of time because I believed the only way I could deal with the comboBox was selected item. So I rewrote a lot of my classes to also return an index. Now I'm mostly working with AS code rather than MXML code and I think my grip on how things work internally is better so its not so much of an issue. I know I should look up the language refrence for all the classes I use but to be honest who really has time for that? </rant> Thanks, Jeffry Regards, Wes On Fri, Apr 3, 2009 at 2:32 PM, Jeffry Houser <[email protected]> wrote: > > Looking at the ComboBox code, it looks like the "inspectable" metadata is > set to none. I assume that hides it from code hinting. > > However, despite that you should be able to use it w/ no problems in MXML > just as you would w/ ActionScript. > > Wesley Acheson wrote: > > Hi, > > Why isn't the ComboBox.selectedItem available in MXML? It would be better > then selectedIndex in many cases. > > Regards, > > Wesley Acheson > > > -- > Jeffry Houser, Technical Entrepreneur > Adobe Community Expert: > http://tinyurl.com/684b5hhttp://www.twitter.com/reboog711 | Phone: > 203-379-0773 > -- > Easy to use Interface Components for Flex > Developershttp://www.flextras.com?c=104 > --http://www.theflexshow.comhttp://www.jeffryhouser.com > -- > Part of the DotComIt Brain Trust > > > > >
