Yes, there is no problem actually with this. Everything works ok. I just wanted to put my own CollapsablePanelGroup (manager that allows only one Panel in group to be in "expanded" state) class right before CollapsablePanel instances, like it's usually done with RadioButtonGroup and RadioButton instances. :)

On 8/22/06, Matt Chotin <[EMAIL PROTECTED]> wrote:

Hmm, I thought we had removed that rule, but it's generally just a parsing restriction.  A faceless component isn't contained by visual containers so it shouldn't be nested inside of them in MXML.

  Beyond coding style this shouldn't really affect you, right?

  Matt

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to