-
I am currently using the toolbar control that comes with the Microsoft Windows Common Controls 6.0 (SP3) OCX (MSCOMCTL.OCX) that comes with Visual Studio. This OCX however comes with a whole host of other controls that I dont need or want in my application.
When I package and distribute this application, the whole OCX is included in the package. This adds to the size of the setup which is annoying, but when I load a form with the toolbar control on it, is the whole OCX loaded into memory, or only the toolbar control itself? The application I am developing really needs to have an absolute minimal amount of resources used.
So, my question is, is there a stand alone OCX version of the toolbar control, or another that has identical or similar functionality, is there a tool I can use to extract this control out of the OCX (is that even legal to do?), or do I really not need to worry about it?
If anyone can offer some insight into this, I would be most appreciative :)
Thanks.
-
Extracting it... not possible.
An alternative.. not that could be possible.
The idea however is that it isn't called "Common Controls" for nothing and chances are will be installed already on any machine you would install your application on so you may have to question whether to include it at all.
Its a thought.
-
Yup, I agree, the actual availability of the control is not likely to be a problem.
My main concern tho is the impact of using a large OCX with all these extra controls in it on a systems resources, ie, is the whole OCX loaded into memory, or just the toolbar control itself, and will that affect the speed of loading or initialising the parts of the application that use it??
Cos if the overhead is too high, would look for an alternative to using that control.
