<div>
Yeah, but what if I want access to the controls as member variables? Don't I need the wrapper classes for that?
</div>


Yeah, but what if I want access to the controls as member variables? Don't I need the wrapper classes for that?

<div>
<div class="content wysiwyg-content">
When you generate a class for, say, a new dialog and you've included some Active X controls, VC6 generates wrapper classes for all of these things that are not standard MFC (ie. COleFont, CPicture, etc...). &nbsp;The annoying thing is, when you create another dialog that uses the same Active X control, VC6 generates ANOTHER wrapper class (say, I had COleFont, it now generates files for COleFont2 which, other than the 2 in the name, are identical)! &nbsp;Is there any way to make VC6 smart so that it knows to use the wrapper already generated. &nbsp;I swear, I can't stand having 30+ files that all do the exact same thing for the exact same control.
</div>
</div>


When you generate a class for, say, a new dialog and you've included some Active X controls, VC6 generates wrapper classes for all of these things that are not standard MFC (ie. COleFont, CPicture, etc...).  The annoying thing is, when you create another dialog that uses the same Active X control, VC6 generates ANOTHER wrapper class (say, I had COleFont, it now generates files for COleFont2 which, other than the 2 in the name, are identical)!  Is there any way to make VC6 smart so that it knows to use the wrapper already generated.  I swear, I can't stand having 30+ files that all do the exact same thing for the exact same control.

Generated Wrapper Classes Duplicates!!!

Kernel and system programming is the process of creating the software necessary for a computer or device to function and operate other programs. Some operating systems (such as Microsoft Windows) are proprietary, but others, such as the various Linux distributions, are open source.