WindowBlinds 6 Beta Feedback
Wednesday, August 1, 2007 by Neil Banfield | Discussion: Stardock Support General
Please post all feedback about the WindowBlinds 6 beta on this thread.
Note that the beta is for 32 bit XP and Vista systems only. Please do not post about it not working on 64 bit XP/Vista. Please continue to use WB 5.51 on those platforms.
This beta is for Object Desktop customers ONLY. Standalone WindowBlinds 5 owners will not be able to activate this build.
Please note that you must have Stardock Central 2.46 Build 154 or later to install the WindowBlinds 6 betas. If you try and use older versions, it'll eventually timeout and give you an error about an invalid URL.
If you have problems with it running at all, please uninstall WB6, reboot and then try reinstalling WB6 again.
 |
|
Page 12 of 27 | |
|
|---|
karmat
Reply #222 Sunday, August 5, 2007 2:15 PM
Reply #222 Sunday, August 5, 2007 2:15 PM
Here's my experiences so far...
I did the first install of WB 6 with no problem except that after it uninstalled WB5, it went into installing WB 6 without rebooting - I had to stop the install and reboot, then install WB6.
Everything worked great! I downloaded a few skins that I had before that were lost in the change, but I didn't try any of them out except for Vista Bug, which I happen to really like right now. Everything is fine up to this point.
I installed the update to WB6 (yesterday?), I thought everything was okay till today when I tried to change a skin and noticed all kinds of stuff wouldn't change...
In Theme Manager; Suites and Visual Styles would change everything except for the Task Bar and Start Menu (they stayed Vista Bug). Icon Packager wouldn't change after the first try. In WindowBlinds, the Task Bar and Start Menu wouldn't change. I reverted back to default Windows Classic on everything. Task Bar and Start Menu were almost Classic, but not quite.
Reboot. Task Bar and Start Menu are now Windows Classic. Visual styles still won't change, Icons and Cursors will change, Boot Skins won't change.
Uninstall WB6. Reboot. Wouldn't startup properly, can't shutdown properly. Turn on, cancel disk check. Starts up okay.
Reinstall WB6 from StartDock Central. It installs, but doesn't reboot as prompted, it just opens WB. Tried to reboot but had to do a manual shutdown. Turn on, skipped disk check, starts up okay. Checked WB6 and Theme Manager, everthing now seems to change as it should. I'm going to try and download some more skins and see if it continues to work as it should.
Hopefully, future updates go smoother, cause I think the program is great!
My system info is (XP Home Edition)...
WindowBlinds version : WindowBlinds 6 (6.0 (beta build 19 x86))
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(Plug and Play Monitor) 1 is attached to Intel(R) 82852/82855 GM/GME Graphics Controller
Wblind.dll 2007/08/03 11:51:20
Wbsrv.dll 2007/08/02 11:25:18
Wbconfig.exe 2007/08/02 11:25:47
Wbload.exe 2007/07/30 13:14:11
Wbhelp.dll 2007/07/24 10:21:07
Wbui.dll 2007/07/24 10:21:06
Tray.dll 2007/07/24 10:21:49
I did the first install of WB 6 with no problem except that after it uninstalled WB5, it went into installing WB 6 without rebooting - I had to stop the install and reboot, then install WB6.
Everything worked great! I downloaded a few skins that I had before that were lost in the change, but I didn't try any of them out except for Vista Bug, which I happen to really like right now. Everything is fine up to this point.
I installed the update to WB6 (yesterday?), I thought everything was okay till today when I tried to change a skin and noticed all kinds of stuff wouldn't change...
In Theme Manager; Suites and Visual Styles would change everything except for the Task Bar and Start Menu (they stayed Vista Bug). Icon Packager wouldn't change after the first try. In WindowBlinds, the Task Bar and Start Menu wouldn't change. I reverted back to default Windows Classic on everything. Task Bar and Start Menu were almost Classic, but not quite.
Reboot. Task Bar and Start Menu are now Windows Classic. Visual styles still won't change, Icons and Cursors will change, Boot Skins won't change.
Uninstall WB6. Reboot. Wouldn't startup properly, can't shutdown properly. Turn on, cancel disk check. Starts up okay.
Reinstall WB6 from StartDock Central. It installs, but doesn't reboot as prompted, it just opens WB. Tried to reboot but had to do a manual shutdown. Turn on, skipped disk check, starts up okay. Checked WB6 and Theme Manager, everthing now seems to change as it should. I'm going to try and download some more skins and see if it continues to work as it should.
Hopefully, future updates go smoother, cause I think the program is great!
My system info is (XP Home Edition)...
WindowBlinds version : WindowBlinds 6 (6.0 (beta build 19 x86))
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
(Plug and Play Monitor) 1 is attached to Intel(R) 82852/82855 GM/GME Graphics Controller
Wblind.dll 2007/08/03 11:51:20
Wbsrv.dll 2007/08/02 11:25:18
Wbconfig.exe 2007/08/02 11:25:47
Wbload.exe 2007/07/30 13:14:11
Wbhelp.dll 2007/07/24 10:21:07
Wbui.dll 2007/07/24 10:21:06
Tray.dll 2007/07/24 10:21:49
sleepydawg
Reply #223 Sunday, August 5, 2007 5:39 PM
Mine was doing the same thing till I turned off WindowsFX. Now it's fine. Seems they just got it (WindowsFX) fixed for five, now they got to fix it for 6. It never ends.
Reply #223 Sunday, August 5, 2007 5:39 PM
using the new Diamond skin with per-pixel borders, I see a black background of the titlebar when maximizing any window. Without allowing per-pixel borders, the background color stays correct (light blue) when maximizing. Is this behaviour intentional or is it a beta problem? (Same problem on two computers, running Windows XP Home both.)
Mine was doing the same thing till I turned off WindowsFX. Now it's fine. Seems they just got it (WindowsFX) fixed for five, now they got to fix it for 6. It never ends.
danioc
Reply #224 Sunday, August 5, 2007 11:02 PM
Hi,
using the new Diamond skin with per-pixel borders, I see a black background of the titlebar when maximizing any window. Without allowing per-pixel borders, the background color stays correct (light blue) when maximizing. Is this behaviour intentional or is it a beta problem? (Same problem on two computers, running Windows XP Home both.)
upeters and sleepydawg
The maximized titlebar background being black is intentional.
Reply #224 Sunday, August 5, 2007 11:02 PM
Hi,
using the new Diamond skin with per-pixel borders, I see a black background of the titlebar when maximizing any window. Without allowing per-pixel borders, the background color stays correct (light blue) when maximizing. Is this behaviour intentional or is it a beta problem? (Same problem on two computers, running Windows XP Home both.)
upeters and sleepydawg
The maximized titlebar background being black is intentional.
Necaradan666
Reply #225 Sunday, August 5, 2007 11:55 PM
Reply #225 Sunday, August 5, 2007 11:55 PM
Seems WB6 is not compatible with Supreme Commander. I couldn't start the game without switching back to Aero.
Daiwa
Reply #226 Monday, August 6, 2007 12:54 AM
Reply #226 Monday, August 6, 2007 12:54 AM
Ran across a new problem with .026 - active window frame right is painting lighter than the source image, by about 20 RGB points.
The image on the left is how WB6Config previews the close button & top portion of the window frame right (correctly). The image in the middle is the source image. The image on the right is the close button & top portion of the window frame right as WB6 applies it to the active window - you can easily see the lighter hue of the two right-most pixel columns (the top portion of window frame right). Using magic pink trans.
Did not notice this until the .026 update, but could have been there before since it is subtle.
The image on the left is how WB6Config previews the close button & top portion of the window frame right (correctly). The image in the middle is the source image. The image on the right is the close button & top portion of the window frame right as WB6 applies it to the active window - you can easily see the lighter hue of the two right-most pixel columns (the top portion of window frame right). Using magic pink trans.
Did not notice this until the .026 update, but could have been there before since it is subtle.
Bichur
Reply #227 Monday, August 6, 2007 2:02 AM
Reply #227 Monday, August 6, 2007 2:02 AM
I'm getting a button glow effect after image when using Diamond.
Mousing over the buttons makes it go away.
If I have multiple windows open, mousing over the button on the other windows have no effect, it has to be the one it originally came from.
Mousing over the buttons makes it go away.
If I have multiple windows open, mousing over the button on the other windows have no effect, it has to be the one it originally came from.
j8m
Reply #228 Monday, August 6, 2007 2:59 AM
Reply #228 Monday, August 6, 2007 2:59 AM
HI ALL, All went well with my instal on XP and had no problems with the themes so far. THANKS toALL AT Stardock 
kin242
Reply #229 Monday, August 6, 2007 3:00 AM
Reply #229 Monday, August 6, 2007 3:00 AM
Leo vista- calendar is not skinned when you expand it from the taskbar... shiny purple colours!
Septimus
Reply #230 Monday, August 6, 2007 7:58 AM
Reply #230 Monday, August 6, 2007 7:58 AM
Working for me now at least 
All is well except.
The rounded taskbar has a solid background behind it thanks to the sidebar. Even when skinned by WB6 this issue still occurs.
All is well except.
The rounded taskbar has a solid background behind it thanks to the sidebar. Even when skinned by WB6 this issue still occurs.
NatSciene
Reply #231 Monday, August 6, 2007 8:46 AM
Reply #231 Monday, August 6, 2007 8:46 AM
Any chance of an x64 version for Vista sometime soon?
~ NatScience
~ NatScience
danioc
Reply #232 Monday, August 6, 2007 8:51 AM
I'm getting a button glow effect after image when using Diamond.
Mousing over the buttons makes it go away.
If I have multiple windows open, mousing over the button on the other windows have no effect, it has to be the one it originally came from.
Bichur, looks like it's a bad skin cash problem, try open the skin folder and delete all files with the extension ".WB4" and reapply the skin.
Working for me now at least All is well except.
The rounded taskbar has a solid background behind it thanks to the sidebar. Even when skinned by WB6 this issue still occurs.
Septimus, the background is looking right looking at first in your screenshot but I can really tell cause this screenshot is too small, could you please like a bigger screenshot of that area?
Reply #232 Monday, August 6, 2007 8:51 AM
I'm getting a button glow effect after image when using Diamond.
Mousing over the buttons makes it go away.
If I have multiple windows open, mousing over the button on the other windows have no effect, it has to be the one it originally came from.
Bichur, looks like it's a bad skin cash problem, try open the skin folder and delete all files with the extension ".WB4" and reapply the skin.
Working for me now at least
All is well except.The rounded taskbar has a solid background behind it thanks to the sidebar. Even when skinned by WB6 this issue still occurs.
Septimus, the background is looking right looking at first in your screenshot but I can really tell cause this screenshot is too small, could you please like a bigger screenshot of that area?
WebGizmos
Reply #233 Monday, August 6, 2007 9:57 AM
Reply #233 Monday, August 6, 2007 9:57 AM
Here's a glitch I ran into with the Diamond skin. The title bar text is way out of alignment.
Kind of disappointing since I was waiting to use this skin. Hope someone can fix this. The other skins that came with it work fine...as do the other skins I have.
Kind of disappointing since I was waiting to use this skin. Hope someone can fix this. The other skins that came with it work fine...as do the other skins I have.
Neil Banfield
Reply #234 Monday, August 6, 2007 10:10 AM
Reply #234 Monday, August 6, 2007 10:10 AM
WebGizmos: Delete all the .WB4 files from the diamond directory and reapply the skin.
Bender50
Reply #235 Monday, August 6, 2007 10:45 AM
Reply #235 Monday, August 6, 2007 10:45 AM
Call me an idiot , but how do i upgrade stardock central?
DadBart
Reply #236 Monday, August 6, 2007 11:34 AM
Reply #236 Monday, August 6, 2007 11:34 AM
I had reported (along with several others) a problem in WB 5.5 not displaying certain dialogs and menus in specific applications. One of them was the Outlook 2007 Rules and Alerts dialog. It showed nothing in the dialog. This problem was reproduced in your support lab and fixed with the last update to WB 5.5.
It is back as a problem in the WB6 beta release.
It is back as a problem in the WB6 beta release.
DadBart
Reply #237 Monday, August 6, 2007 11:35 AM
Reply #237 Monday, August 6, 2007 11:35 AM
Sorry, the dialog problem I reported above is on 32bit Vista.
Cavan1
Reply #238 Monday, August 6, 2007 11:59 AM
Hey Neil, it is the skin, maybe an older work in progress version slipped in?, I had to adjust y offset for buttons from 16 to 2, had to adjust content top margin for caption and maxed caption from 12 to 0.
The 2 for button offset is the setting in the Vista sub skin, top content margin in it is 1.
Was just the buttons in per pixel section, the free form buttons are at y offset of 0.
A couple questions out of curiosity 1) why was Diamond made in UIS1+ format, 2) since in the Window Borders section there are no non per pixel images, where are the images called from for in a MDI app.
Reply #238 Monday, August 6, 2007 11:59 AM
Delete all the .WB4 files from the diamond directory and reapply the skin.
Hey Neil, it is the skin, maybe an older work in progress version slipped in?, I had to adjust y offset for buttons from 16 to 2, had to adjust content top margin for caption and maxed caption from 12 to 0.
The 2 for button offset is the setting in the Vista sub skin, top content margin in it is 1.
Was just the buttons in per pixel section, the free form buttons are at y offset of 0.
A couple questions out of curiosity 1) why was Diamond made in UIS1+ format, 2) since in the Window Borders section there are no non per pixel images, where are the images called from for in a MDI app.
WebGizmos
Reply #239 Monday, August 6, 2007 12:14 PM
Thanks Neil! That did the trick! So...was this skin started with WB4 and the files were left in? 
One thing that happened after deleting the WB4 files is nothing shows in the WB Config list for Diamond now...no biggy cause the skin works...but thought you or the author would like to know.
Reply #239 Monday, August 6, 2007 12:14 PM
WebGizmos: Delete all the .WB4 files from the diamond directory and reapply the skin.
Thanks Neil! That did the trick!
So...was this skin started with WB4 and the files were left in? 
One thing that happened after deleting the WB4 files is nothing shows in the WB Config list for Diamond now...no biggy cause the skin works...but thought you or the author would like to know.
Neil Banfield
Reply #240 Monday, August 6, 2007 12:25 PM
Reply #240 Monday, August 6, 2007 12:25 PM
It looks like your diamond skin has been corrupted. It is a UIS2 skin, not a UIS1 skin.
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!
|
|
Page 12 of 27 | |
|
|---|
Reply #221 Sunday, August 5, 2007 12:57 PM
Thank you.