TabControlExt paint problems (2.0 beta)

This happens only if my splash form is displayed, if I disable that this never happens. The splash form is started on a seperate background thread and is closed when the main form is done loading. Hope this helps, if not feel free to ask me for further help. Looking forward to the next beta :)

Hi Sigurdur, I have put together a sample_application in v2.0.1.0 (2.0 beta) as per your specifications above and the TabControlExt seems to have no painting issues when ThemesEnabled is set to true. Please take a look at the sample and let me know if this meets your requirements. If not, kindly modify it show above mentioned the painting error. We appreciate your cooperation and thanks for choosing Syncfusion products. Regards, Guru Patwal Syncfusion, Inc.

Hi, Sorry for the late reply, just got back to work today after a small vacation. Here is your sample modified to show the behaviour I mentioned. Fyrst try to compile a DEBUG build and start it with debugging (F5) and it works ok. Then try a RELEASE build and start without debugging (CTRL+F5) and it bums out :P I wasn''t using the splash component from you but another method, and something in there is causing this. TabControlAdv_test_9976_NEW_8401.zip

Hi Sigurdur, Thanks for the update and for the modified sample application. I could observe the above mentioned problem here when your sample was compiled in ''Release'' mode. However, we will further investigate this and I will keep you informed regarding the developments. Thanks for your patience. Regards, Guru Patwal Syncfusion, Inc.

This is still happening in the RC1 release (2.0.3.0), could you give me an update on this?

Hi Sigurdur, After having consulted the development team in this regard, I would like to inform the following : The problem seems to be that the EnableVisualStyles call does not work as intended if some code is executed before the application starts. In this case, you are starting a thread to display your own form as a Splash screen. It does not use our SplashControl, but we suspect that the same problem could occur even if it does. One of our users had a similar problem sometime back and Microsoft had provided them with a solution. We have requested the user for information regarding this solution, and I will update you on this as we hear from them. We appreciate your patience and cooperation. Regards, Guru Patwal Syncfusion, Inc.

I''ve tried one of the recommended fixes, run "Application.DoEvents();" just before the Application.Run(). That fixes some VisualStyles problems, but not this one. I''ve also tried doing this before I spawn the splash thread and tried changing the order of things in the startup sequence but nothing works. What would you recommend? the reason I do it this way is that I want the splash form up on the screen ASAP, and this way helps me get it before the main form is even loaded. Any tips or ideas are greatly appreciated :)

Just to let you know, I''ve found a solution. It involves manually setting up an ApplicationContext and using the Application.Idle event to initialize the context. If anyone is interesting in the details send me an email at sigurdg(at)kbbanki.is

Hi Sigurdur, Thanks for sharing this information with us. We are glad that you could work around this problem. Please let us know if you need any other information. Regards, Guru Patwal Syncfusion, Inc.

Some people have asked me for this solution, so here is a quick sample. It may not be the best way, but it works :) AppLoader_demo_189.zip

Sorry but this still doesn''t seem to work. >Some people have asked me for this solution, so here is a quick sample. It may not be the best way, but it works :) > > > >AppLoader_demo_189.zip > >

All these problems are solved via the use of a manifest as Application.EnableVisualStyles is simply poorly implemented. End of story. >Sorry but this still doesn''t seem to work. > >>Some people have asked me for this solution, so here is a quick sample. It may not be the best way, but it works :) >> >> >> >>AppLoader_demo_189.zip >> >>