With what you suggested, it changes the state to a blank screen, instead of showing the state it should have called.
Here is what I am trying now. function menuHandler(oEvent:Object) { currentState = oEvent.menuItem.data; } --- In flexcoders@yahoogroups.com, "Joan Tan" <[EMAIL PROTECTED]> wrote: > > Try oEvent.menuItem.data instead of the getProperty syntax. > > Joan > > -----Original Message----- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Rottman > Sent: Tuesday, March 28, 2006 10:44 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: Menu Bar Killing me. Can someone help. > > Joan, I added what you said, and it now formats my bar correctly to > the menubar. But now my menuhandler function no longer works. It is > setup that that it changes the states when a child menuitem is > selected. Any idea why this wont work now. > > function menuHandler(oEvent:Object) { > currentState = oEvent.menuItem.getProperty("data"); > } > > > > --- In flexcoders@yahoogroups.com, "Joan Tan" <tan@> wrote: > > > > There are known issues in the beta for MenuBar. Here is the text > from the known issues page on labs: > > > > MenuBar not working with e4x XML dataProvider The MenuBar shows the > first node's children as the top level instead of showing the entire > data structure. > > > > Issues with MenuBar and inline XML that includes a rootNode MenuBar > does not display correctly when you use well formatted inline XML that > includes a rootNode. if you are using inline XML as the dataProvider > for your MenuBar, you have the following options: > > > > Do not use a root node for your XML; use showRoot="false" and > labelField="@label" > > If you have a root node for your XML, the XML must use format="e4x" > , your dataProvider must include the root (for example, > dataProvider="{myXML.root}") , and you must specify showRoot="false" > and labelField="@label" > > > > http://labs.macromedia.com/wiki/index.php/Flex:Known_Issues > > > > joan > > > > -----Original Message----- > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] > On Behalf Of Sönke Rohde > > Sent: Tuesday, March 28, 2006 10:06 AM > > To: flexcoders@yahoogroups.com > > Subject: RE: [flexcoders] Re: Menu Bar Killing me. Can someone help. > > > > Hi Peter, > > In my case this doesn't change anything and all my nodes have a > > label-attribute. > > > > Cheers, > > Sönke > > > > > -----Original Message----- > > > From: flexcoders@yahoogroups.com > > > [mailto:[EMAIL PROTECTED] On Behalf Of Peter Blazejewicz > > > Sent: Tuesday, March 28, 2006 8:01 PM > > > To: flexcoders@yahoogroups.com > > > Subject: [flexcoders] Re: Menu Bar Killing me. Can someone help. > > > > > > Hello Jeremy, > > > > > > try to add labelField property declaration, > > > e.g.: > > > <mx:MenuBar labelField="@label" .... > > > > > > to filter data for dataProvider, > > > > > > hth, > > > regards, > > > Peter Blazejewicz > > > > > > > > > > > > > > > > > > -- > > > Flexcoders Mailing List > > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > Search Archives: > > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/