NEVER EVER EVER EVER use view classes as controllers or presenters of other view classes . I've still got shrapnel in my leg from the last project where that was the main design theme.
If you need to manage view classes you can make presenters, which have no knowledge of the view class. It's very easy to do especially with Flex's databing (including two-way). Or you may opt out for a controller, by adding an interface to the Component B/Component C tandem. That way if you do decide to make C part of B you don't break everything.
OK, I understand your point - especially since what I'm doing is not working! But what do you mean by
I learned my lesson about controlling a parent component from a child. I suppose this could be done, but it would probably be convoluted.
I moved all the code from C into an AS file and copied C's graphic elements into B. Everthing is working fine now.
Thanks again Mr. Penguin.
1 person found this helpful
Paul Williams can explain it better than I can. His blog has MANY writings on the merits and demerits of the various design patterns.