Microsoft and their failure to fix 5 year old bug

  • Thread starter Thread starter schoenfeld1
  • Start date Start date
S

schoenfeld1

How many more years will it take for the geniuses at Microsoft to fix
the TabPage control so it uses the proper xp-theme when specified to do
so?

I'm betting another 5 to 7, how about you?
 
How many more years will it take for the geniuses at Microsoft to fix
the TabPage control so it uses the proper xp-theme when specified to do
so?


The TabControl of .NET 2.0 will support visual styles.
 
Herfried said:
The TabControl of .NET 2.0 will support visual styles.

And the reason Microsoft has not provided a trivial fix for this is...?

People pay large sums of money for VS.NET and they can't even write XP
themed windows form that contains a tab control. (LOL)

Seems like Microsoft don't even use their own .NET for building
applications.

For anyone that needs to write software with .NET, check out:
http://www.skybound.ca/developer/visualstyles/default.aspx

Apparantly one can make a viable business model by selling bug fixes
for Microsoft products.


This poster looks forward to google's sponsorship of mono.



 
Herfried K. Wagner said:
The TabControl of .NET 2.0 will support visual styles.

Yes, it does support Visual Styles, but, just try to set the Tabs locations to any other than the Top. Put them on the bottom ,
left or right side and the tabs will appear but, the text you specify for the tabs will be gone.
Reported as a bug and was told it was a known issue and probably won't be fixed by the release date. As a work around, I was
told to turn off Visual Styles !! Which I did, and that didn't work either. So, even though 2.0 & 2005 are soon to be released
(so they say!) , there are still a lot of bugs.
james
 
Mick said:
TabControlEX is a modified version of TabControl and is available free from
my Controls page.
It fully supports Visual Styles but needs a minimum of framework 1.1 since
it was built in VS2003.

http://dotnetrix.co.uk/controls.html

Nice control. Unfortunately it has a bug(s) which seem to
rearrange/destroy other controls in the form.

Example 1: I added your TabControl to a form and 2 buttons beneath the
tab control. After a few runs it moved the second button to the top
left of the screen and made the Text property an empty string.

Example 2: The last tab page did not appear in the main tab control. I
looked at the InitializeComponent method and it seems your designer
removes the .Add(tabPage) for that tabpage.

I'd be willing to bug fix it if you supplied sourc code.
 
I've never experienced or heard of these bugs before. I have had other bugs
which only popped up when using other third party controls with custom
designers, but these have been traced and sorted. Obviously, I can't trace a
bug that I have never seen or can't reproduce.

Contact me via my site and I will send you a copy of the source if you want
it, but it is only available in VB. I put source on my site in both VB and
C#, but there would be too much code to maintain twice for TabControlEX and
that is the only reason that the source is not posted on the site.

There's nothing special going on in the designer though, that you can't see
in my 'TabControl using Custom Tabpages' example, other than adding two
tabpages to the control in its OnSetComponentDefaults() method.
 
Back
Top