Results 1 to 2 of 2

Thread: Dumb Question about InitCommonControlsEx and ICC_ALL_CLASSES

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Mar 2011
    Posts
    118

    Dumb Question about InitCommonControlsEx and ICC_ALL_CLASSES

    Just wondering, I've read a few posts regarding InitCommonControlsEx and noted a ton of the ICC_bla_bla consts being declared, and almost all of them have ICC_ALL_CLASSES in the declarations, and it's noted that it encompasses all of the other ICC_bla_blas...

    ...yet everyone seems to only use a specific one, two, or even three of the ICC_whatevers and not use ICC_ALL_CLASSES.

    I'm just wondering why not use the ALL_CLASSES? What is the real advantage in picking out the specific ICC(s) corresponding to only what is contained in your project? Is it a memory issue or something like that and if so, does it really make that big of a difference?

  2. #2
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: Dumb Question about InitCommonControlsEx and ICC_ALL_CLASSES

    The only time you have any need to call InitCommonControlsEx at all is when you are creating Win32 control from scratch via API calls.

    VB controls and those in OCXs take care of loading any required control classes themseves.

    So if you are calling InitCommonControlsEx merely in relation to using the Common Controls 6.0 library by selecting this assembly via a manifest...

    ... simply call InitCommonControls instead.

    The only purpose of these calls to to get the library to load, the call itself is not important.


    Of course you can disregard those comments if you really are creating Win32 controls from dirt. But then you'd know what classes to load, and avoid loading the ones you don't need: they take up resources.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width