Has anybody seen this / Solved the puzzle ?
If so, please share your wisdom!
Cheers
Michael.
Alternatively, create the frame through API and add the child controls to
the frame at run time.
"Michael Hansen" <m...@it-online.dk> wrote in message
news:#CcDsgGECHA.1880@tkmsftngp04...
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002
Now I can of course work around this behaviour by moving all my
OptionButtons from Frame's and onto the Form's.
The price being paid is of course that moving/enabling/disabling etc the
group of controls that used to be contained in a frame become more of a
hassle
Cheers
Michael.
"Michael Hansen" <m...@it-online.dk> wrote in message
news:#CcDsgGECHA.1880@tkmsftngp04...
Do you know of other "problems/controls" one should be aware of when
"theming" a VB6 app?
"Mick Doherty" <mdau...@ntlworld.com> wrote in message
news:#mLI7AHECHA.2296@tkmsftngp05...
"Michael Hansen" <m...@it-online.dk> wrote in message
news:eM6bYRHECHA.1108@tkmsftngp04...
Other problems that you can avoid:
When adding MS Common Controls use version 5 not 6. Version 6 controls have
the wrong Classnames and so windows will not apply visual styles.
The exception to this rule is the Rebar Control which is not available in
version 5.
When you add a Rebar control you must also add another of the extended
Common controls.(i.e. Toolbar, ImageList).
When creating your own ActiveX Control You must add one of the extended
Common Controls (I add an empty ImageList as this is non obtrusive and adds
no size to the control.).
Failure to add an extended Common control will result in a Memory Access
error on unloading the compiled executable.
There is a lot to learn now that you wish to program for WinXP
compatibility.
"Michael Hansen" <m...@it-online.dk> wrote in message
news:#oEIHYHECHA.1700@tkmsftngp04...