>>Harry,
>>"Baseclass" is always VFP's. You can only change class. With a commandgroup you would only able to change existing (or added via buttoncount) buttons' properties add/edit methods-events. It's not a container type that you could add other controls (subclassed commandbuttons). If you want to make it instead of a commandgroup use a container and add buttons to it (see txtbtns in wizstyle.vcx). But with a commandgroup you could use setall for properties and use commandgroup events-methods for global methods-events (ie: no click code to buttons but edit commandgroup's click instead).
>>Cetin
>
>thanks for the reply.
>I think I understand most of it but are you saying that you can't create a subclassed commandgroup that uses your own subclassed command buttons?!
>
>Harry
Nearly. What I thought is you are referring to designtime adding of buttons and later changing them in vcx.
That way you can subclass the commandgroup but not buttons in it. When you try to add a subclassed button (or baseclass) you'll get a message "you cannot add ... to non-container ... ". Non-container ???? All docs say commandgroup is a container that you can add buttons to. ie: For optiongroup too it would be the case. But docs say they are containers, they have addobject method then they should really be containers. Well yes they are. You could add your subclassed button programmatically but unfortunately you cannot save it as a class.
Workaround is to put subclassed buttons in a container. You wouldn't lose much doing that way.
Cetin