>For example: I have a container superclass that I subclass into containers for each wizard step. I add the controls for each step to the container subclass. (I then have a pageframe class that subclasses the step containers.) In this case the container superclass just sets the layout information. I don't add any custom properties or methods. Is this an example (even if a bad one) of a Facade structural pattern? I looked at Template, but to me it's not a behavioral pattern.
Speaking purely from "book-learning", this sounds something like a State pattern. Each step in your wizard is a different state and you have a different class of your container for each step. The theory is that this pattern is a way to create objects whose behavior is state-dependant without using conditional statements. (yeah right!) HTH.
----------
Mark Bucciarelli