Hi!

When TabPage.Alignment property is changed at runtime tabs are not displayed
correctly i.e. text is not displayed and visual style changes to something
not seen with any of the available styles. It has been reported many times
by different users. After googling for some time (can I use this word on MS
forums?) I found short explanation for a reason. Setting Alignment property
causes control to be destroyed and recreated with new handle and setting it
with container causes the whole mess. However, I have not found any hints on
solution to this problem.

Are there any KB articles describing this issue or is there any solution to
that problem?

Re: TabPage Alignment property change at runtime problems/bug by Jacek

Jacek
Sun Nov 13 13:30:17 CST 2005

Hi!

Just to inform all others that this is bug reported for COM TabConctrol v6
which is exposed by .NET Framework - all versions including v2.0!!!. And as
MS said they have had no time to fix it (check info in duplicate bugs
discussions as the link below points to freshly created bug consolidating
all other cases). It is just scandalous that for so many years such a simple
bug was not fixed in Windows code.

http://lab.msdn.microsoft.com/ProductFeedback/ViewFeedback.aspx?FeedbackID=5a3bf97f-db1d-49b9-8893-e5a210c8d785

Cheers to all coders at MS


U¿ytkownik "Jacek" <shield_infodate@aster.pl> napisa³ w wiadomo¶ci
news:%23GQCcfH6FHA.2552@TK2MSFTNGP10.phx.gbl...
> Hi!
>
> When TabPage.Alignment property is changed at runtime tabs are not
> displayed correctly i.e. text is not displayed and visual style changes to
> something not seen with any of the available styles. It has been reported
> many times by different users. After googling for some time (can I use
> this word on MS forums?) I found short explanation for a reason. Setting
> Alignment property causes control to be destroyed and recreated with new
> handle and setting it with container causes the whole mess. However, I
> have not found any hints on solution to this problem.
>
> Are there any KB articles describing this issue or is there any solution
> to that problem?
>