Comments on: Nested child nodes within custom MXML components in Flex

By: MALCOLM GODDING

MALCOLM GODDING — Fri, 13 May 2011 07:48:14 +0000

Hello there there! I am satisfied I identified this blog. We have bookmarked it to examine back normally. Finest regards.

By: jocabola

jocabola — Tue, 09 Mar 2010 10:34:31 +0000

Thanks for sharing this Brent!
Love to see this post is helping some people…

By: E Brent Nelson

E Brent Nelson — Fri, 05 Mar 2010 23:43:48 +0000

I had some issues when I tried to add a mx:Form component to this implementation. I resolved them by doing something like this:

http://tinyurl.com/ykq669p

It works great! Thanks.

By: Lacy Garrison

Lacy Garrison — Thu, 14 Jan 2010 03:27:51 +0000

Amazing! Thanks you.

By: Andre

Andre — Sat, 02 Jan 2010 14:30:49 +0000

Thanks, this was just what i needed ;-))

By: Karl

Karl — Thu, 20 Aug 2009 11:21:37 +0000

exactly what i was looking for and really clearly explained. nice to actually learn something!!!!
thanks for doin that :D

By: Cute Squirting

Cute Squirting — Tue, 04 Aug 2009 10:25:46 +0000

nice! i’m gonna make my own journal

By: Danny Kopping

Danny Kopping — Mon, 06 Jul 2009 07:40:05 +0000

Thanks man! Helped me a lot… Just what i was looking for.

By: jocabola

jocabola — Mon, 04 May 2009 10:18:37 +0000

Hi Richard,

never tried to use this further on a subclass or child of the main component.
Notice that this is just a workaround, the best solution I could find searching the net.

I have been using this without problems always facing it the same way:

1) Create a “complex” component with a desired nesting point for the child MX components

2) Use it as a regular component, being able to nest MX components such as buttons, text fields, etc. on the desired nesting point

Notice that the nested elements will be layouted according to your nesting element definitions (vertical, horizontal, absolute, …)

Once again, never tried to add a second nesting level, although I guess it should work as well.

Cheers,

By: Richard C Haven

Richard C Haven — Wed, 22 Apr 2009 23:59:28 +0000

I cannot get this to work beyond the first generation: a sub-class of this component cannot incrementally add children, even if I duplicate the DefaultProperty protocol.

I’m coming from Delphi’s visual component inheritance, and this seems a bit rough.

Cheers