Problems with Visual Studio 6.0
Friday, January 7, 2005 by Carpe__Diem | Discussion: WindowBlinds
Hello all,
I have this problem with Visual Studio 6.0 it might have always been a problem and I just noticed it the other day. (Now that I have noticed it, it really bugs me to the point that I have stopped using Windowblinds.)
I happen on all skins, when you minimize or max the app (in either SDI or MDI mode) it will loose its skin for a fraction of a second (looks like windows classic) then return skinned. This is the only program that exhibits this behavior.)
This does not happen with luna, or any of the hacked Visual Styles. (I prefer WB but just can not stand the repainting of Visual Studio 6.0)
I tried turning off animate windows when min or max, but it still happens.
I’m running a Dell 600 laptop with an ATI 9000 Radeon video card.
Thanks in advance!
I have this problem with Visual Studio 6.0 it might have always been a problem and I just noticed it the other day. (Now that I have noticed it, it really bugs me to the point that I have stopped using Windowblinds.)
I happen on all skins, when you minimize or max the app (in either SDI or MDI mode) it will loose its skin for a fraction of a second (looks like windows classic) then return skinned. This is the only program that exhibits this behavior.)
This does not happen with luna, or any of the hacked Visual Styles. (I prefer WB but just can not stand the repainting of Visual Studio 6.0)
I tried turning off animate windows when min or max, but it still happens.
I’m running a Dell 600 laptop with an ATI 9000 Radeon video card.
Thanks in advance!
Carpe__Diem
Reply #2 Wednesday, January 19, 2005 11:02 AM
I wrote support about it, and VS 6.0 & VS.NET are not compatible with Windowblinds.
Pity, but I guess I will have to continue using StyleXP.
Reply #2 Wednesday, January 19, 2005 11:02 AM
| I have the same problm too. I also see the Windows Classic skin for a moment. Quite annoying... |
I wrote support about it, and VS 6.0 & VS.NET are not compatible with Windowblinds.
Pity, but I guess I will have to continue using StyleXP.
Neil Banfield
Reply #3 Wednesday, January 26, 2005 10:16 AM
Reply #3 Wednesday, January 26, 2005 10:16 AM
Support said WB wasn't compatible with VC6 and VS.net?
Carpe__Diem
Reply #4 Wednesday, January 26, 2005 4:14 PM
Reply #4 Wednesday, January 26, 2005 4:14 PM
yep, here is the email:
------------------------------------------------
Hi,
Windowblinds can only successfully skin programs that use the Windows API's to draw its windows.
if you go into the Windowblinds Config and select the "Per Application" option, add an exclusion for Visual Studio. This will
stop Windowblinds from skinning Visual Studio while it is loaded.
Thanks,
Nick
===================================================
Stardock Support
17292 Farmington Rd
Livonia, MI 48152
United States
Phone:
(734) - 762 - 0687
FAX
(734) - 762 - 0690
For best results, use Stardock's news server:
news://news.stardock.com and visit the appropriate news group.
https://www.stardock.com
------------------------------------------------
Hi,
Windowblinds can only successfully skin programs that use the Windows API's to draw its windows.
if you go into the Windowblinds Config and select the "Per Application" option, add an exclusion for Visual Studio. This will
stop Windowblinds from skinning Visual Studio while it is loaded.
Thanks,
Nick
===================================================
Stardock Support
17292 Farmington Rd
Livonia, MI 48152
United States
Phone:
(734) - 762 - 0687
FAX
(734) - 762 - 0690
For best results, use Stardock's news server:
news://news.stardock.com and visit the appropriate news group.
https://www.stardock.com
NixonMcJinx
Reply #5 Thursday, January 27, 2005 4:13 PM
Reply #5 Thursday, January 27, 2005 4:13 PM
My bad. On second thoughts that exclusion was a bit too extreme of a solution.
Often, skins with maximizing problems are using MaxBorderCut values that they shouldn't. Another skin shouldn't have the problem.
-- Nick
Stardock Support
Often, skins with maximizing problems are using MaxBorderCut values that they shouldn't. Another skin shouldn't have the problem.
-- Nick
Stardock Support
Gallus
Reply #6 Thursday, January 27, 2005 5:50 PM
Reply #6 Thursday, January 27, 2005 5:50 PM
Hi,
There is an application named STOIK Video Converter 2.
Some skins are compatible with it, but some aren't. This kind of issue could not happen. I think WB should handle this kind of situation better.
Skins that work without problem: FlyOS, Element Default and Royale
Skins that make STOIK window bigger and bigger (it's a funny effect, but the application turns useless): Mozilla, Anomaly Orthodox, Pix Office, XP Corona
Maybe, considering STOIK and the fact that some skins work and others don't, you could find what configuration causes this and what WB could do to avoid that.
WB should give us a basic skin support at least, like Windows XP and, then, give us a little more (the WB plus).
Thanks!
There is an application named STOIK Video Converter 2.
Some skins are compatible with it, but some aren't. This kind of issue could not happen. I think WB should handle this kind of situation better.
Skins that work without problem: FlyOS, Element Default and Royale
Skins that make STOIK window bigger and bigger (it's a funny effect, but the application turns useless): Mozilla, Anomaly Orthodox, Pix Office, XP Corona
Maybe, considering STOIK and the fact that some skins work and others don't, you could find what configuration causes this and what WB could do to avoid that.
WB should give us a basic skin support at least, like Windows XP and, then, give us a little more (the WB plus).
Thanks!
Carpe__Diem
Reply #7 Friday, January 28, 2005 9:51 AM
Reply #7 Friday, January 28, 2005 9:51 AM
Nick:
"It happens on all skins, when you minimize or max the app (in either SDI or MDI mode) it will loose its skin for a fraction of a second (looks like windows classic) then return skinned. This is the only program that exhibits this behavior."
---------------
My bad. On second thoughts that exclusion was a bit too extreme of a solution.
Often, skins with maximizing problems are using MaxBorderCut values that they shouldn't. Another skin shouldn't have the problem.
-- Nick
Stardock Support
-----------------
As you can see I have tried many skins and still the same. Also as mentioned it happens when you minimize the app. Your first solution seems to be the only one.
Do you have a stkin that you think will work that I could try?
Thanks!
pg2ssi
"It happens on all skins, when you minimize or max the app (in either SDI or MDI mode) it will loose its skin for a fraction of a second (looks like windows classic) then return skinned. This is the only program that exhibits this behavior."
---------------
My bad. On second thoughts that exclusion was a bit too extreme of a solution.
Often, skins with maximizing problems are using MaxBorderCut values that they shouldn't. Another skin shouldn't have the problem.
-- Nick
Stardock Support
-----------------
As you can see I have tried many skins and still the same. Also as mentioned it happens when you minimize the app. Your first solution seems to be the only one.
Do you have a stkin that you think will work that I could try?
Thanks!
pg2ssi
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Tuesday, January 18, 2005 5:53 PM
I have the same problm too.
I also see the Windows Classic skin for a moment. Quite annoying...
But I also have another issue with VB6 and WB:
I use my Windows taskbar at the top of the screen. When I use VB6 maximized and then I minimize it the title bar of VB6 goes behind the Windows taskbar. I have to restore the VB6 window and then maximize it again.
That's really annoying!!
This issue happens with some TuneUp applications too (e.g. Tuneup Registry Editor).