Command Window skinned differently
Thursday, March 18, 2004 by alpha-prime | Discussion: Stardock Software
I seem to have got my WindowBlinds into a mess in that the command window is always skinned with the same skin (pixoffice) no matter what skin I use within WindowBlinds.
If I unload WindowBlinds all windows including the command window are back to standard Windows classic look.
If I then start WindowBlinds and pick any skin the command window comes up always skinned in pixoffice. This is true even if I uncheck skin console window within WindowBlinds.
I can either have no WindowBlinds and have standard windows, or start WindowBlinds and the command window is always skinned in Pixoffice, no matter what the skin I am using or whether skin console window is checked or not.
Any ideas how to correct this?
I am running Windows XP Pro with SP1 and WindowBlinds 4.20.019
Many thanks
If I unload WindowBlinds all windows including the command window are back to standard Windows classic look.
If I then start WindowBlinds and pick any skin the command window comes up always skinned in pixoffice. This is true even if I uncheck skin console window within WindowBlinds.
I can either have no WindowBlinds and have standard windows, or start WindowBlinds and the command window is always skinned in Pixoffice, no matter what the skin I am using or whether skin console window is checked or not.
Any ideas how to correct this?
I am running Windows XP Pro with SP1 and WindowBlinds 4.20.019
Many thanks
alpha-prime
Reply #2 Friday, March 19, 2004 12:50 PM
Reply #2 Friday, March 19, 2004 12:50 PM
I checked out the per application setting, removed all other apps and still the command window is always skinned with Pixoffice. I can not remove this:
1) I have tried several different WindowBlind skins and the command window remains skinned in PixOffice.
2) I have tried disabling and enabling skin command window within Windowblinds to no effect. Even if skin command window is turned off in WindowBlinds it is still skinned using PixOffice.
3) I then removed the PixOffice skin via WindowBlinds, rebooted and still the command window is skinned in Pixoffice. How can this be after deleting the skin?
Any help on how to correct this greatly appreciated. It is driving me nuts!
Information:
XP Pro with service pack 1
WindowBlinds version 4.20.019
Pentium IV 2.5 Ghz processor
64MB DDR Nvidia GeForce4 Ti4200
Graphics driver version 52.16
[Message Edited]
1) I have tried several different WindowBlind skins and the command window remains skinned in PixOffice.
2) I have tried disabling and enabling skin command window within Windowblinds to no effect. Even if skin command window is turned off in WindowBlinds it is still skinned using PixOffice.
3) I then removed the PixOffice skin via WindowBlinds, rebooted and still the command window is skinned in Pixoffice. How can this be after deleting the skin?
Any help on how to correct this greatly appreciated. It is driving me nuts!
Information:
XP Pro with service pack 1
WindowBlinds version 4.20.019
Pentium IV 2.5 Ghz processor
64MB DDR Nvidia GeForce4 Ti4200
Graphics driver version 52.16
[Message Edited]
Kevin_C
Reply #3 Saturday, March 20, 2004 5:55 PM
Reply #3 Saturday, March 20, 2004 5:55 PM
I'm seeing this too and I haven't setup any per-application skinning. I've tried disabling Command Prompt skinning and it still skins the command prompt and I can't ever get the skin to change.
alpha-prime
Reply #4 Sunday, March 21, 2004 10:37 AM
Reply #4 Sunday, March 21, 2004 10:37 AM
Sorry to hear you have the same issue f0r3.
Normally these forums have answers to most problems, so I guess the lack of input suggests it is a bug in WindowBlinds in some way. I have emailed stardock support, hopefully they will reply after the weekend.
Normally these forums have answers to most problems, so I guess the lack of input suggests it is a bug in WindowBlinds in some way. I have emailed stardock support, hopefully they will reply after the weekend.
bussie
Reply #5 Monday, March 22, 2004 1:50 AM
Reply #5 Monday, March 22, 2004 1:50 AM
Hi,
Which exe are you trying to skin?
Here it is working just fine, with every skin that i want.
c:\windows\system32\cmd.exe
Which exe are you trying to skin?
Here it is working just fine, with every skin that i want.
c:\windows\system32\cmd.exe
Shameless Designs
Reply #6 Monday, March 22, 2004 12:01 PM
I don't recognize that version number, but that may be because I use the beta versions. Have you updated your WindowBlinds thru SDC lately? There have been a lot of updates and bugfixes in the past couple of weeks.
Reply #6 Monday, March 22, 2004 12:01 PM
| #2 by alpha-prime Information: XP Pro with service pack 1WindowBlinds version 4.20.019Pentium IV 2.5 Ghz processor64MB DDR Nvidia GeForce4 Ti4200Graphics driver version 52.16 |
I don't recognize that version number, but that may be because I use the beta versions. Have you updated your WindowBlinds thru SDC lately? There have been a lot of updates and bugfixes in the past couple of weeks.
alpha-prime
Reply #7 Monday, March 22, 2004 12:59 PM
Reply #7 Monday, March 22, 2004 12:59 PM
Yes, I have latest general release version of WindowBlinds: version 4.20.019 according to SDC.
The command window just refuses to change its skin. What really puzzles me is that I removed the skin using WindowBlinds, and still the command window is skinned using it. There must be some special treatment of the command window.
[Message Edited]
The command window just refuses to change its skin. What really puzzles me is that I removed the skin using WindowBlinds, and still the command window is skinned using it. There must be some special treatment of the command window.
[Message Edited]
alpha-prime
Reply #8 Thursday, April 29, 2004 2:55 PM
Reply #8 Thursday, April 29, 2004 2:55 PM
I followed the advice of GreenReaper over on the SDC chat and deleted WindowBlinds, cleaned out the WindowBlinds keys in the registry and reinstalled WindowBlinds.
This cured the issue with the command window always been skinned in one skin. Alas, after several changes of skin the problem comes back and the command window gets stuck in one skin again!
At least it is relatively easy to get out of this problem, deleting WB doesn't delete the skins so reinstallation is not too involved. Even so it would nice if there was a fix for this in a future release.
p.s. since this issue started I have upgraded my graphics driver to Nvidia version 56.64.
This cured the issue with the command window always been skinned in one skin. Alas, after several changes of skin the problem comes back and the command window gets stuck in one skin again!
At least it is relatively easy to get out of this problem, deleting WB doesn't delete the skins so reinstallation is not too involved. Even so it would nice if there was a fix for this in a future release.
p.s. since this issue started I have upgraded my graphics driver to Nvidia version 56.64.
moshi
Reply #9 Friday, April 30, 2004 6:41 AM
Reply #9 Friday, April 30, 2004 6:41 AM
as you seem to use your command line often, i suggest to to try out this program: http://sourceforge.net/projects/console/
not only does it give you plenty of customizing options as the common X consoles do, but your problems should also not happen with this app and even the scrollbar will be skinned. (at least it does so with msstyles, will probably work just as well with WindowBlinds.)
not only does it give you plenty of customizing options as the common X consoles do, but your problems should also not happen with this app and even the scrollbar will be skinned. (at least it does so with msstyles, will probably work just as well with WindowBlinds.)
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 Thursday, March 18, 2004 6:43 PM