The german startmenu issue is fixed as far as we know. Regarding the person who had the reboot, if they made the window semi transparent and then rolled it up then their PC may reboot due to an OS bug. There is little we can do about this one and Microsoft will need to fix it. This also occured with WB 4.0.
WindowBlinds does not replace uxtheme.dll ever. Your non signed msstyles will not show up in the appearance tab when WB is installed as WB will only show WB themes + the valid msstyle files and WB has worked like this since the first alphas of WB3 (at the time there were only signed msstyles) Holding down ctrl when loading display properties will disable the WB features and allow you to access any unsigned msstyle files you have also installed.
WinCustomize Forums
Settings marked deprecated will still work with WB4, but there are new sections which offer improvements and will override the older section/attribute if they are included. Its very unusual for us to break compatibility which is why the old sections will still work fine but without the new features. This means you can still use the old WB3 sections if you really want.
I can assure you it was not intentional and we are working on the fix. While its only 3-4 lines thats causing the issue, we have to test it and build installers & test those out before we can update it. Plus the problem occured over a weekend which also delayed things.
A radeon 9500/9700 card will run windowfx transitions fine in best mode. You need to ensure you have the catalyst 3.4 drivers from ATI (latest drivers) and in the performance page of WindowFX you may need to press a button to enable hardware support. Then reboot and it should run well
That usually means the skinner forgot to set trans = 1 when they used perpixel alpha blending or transparency. WB4 is much more understanding of mistakes like that than WB3 is. A correct WB4 skin should work on WB 3.x too (but without the new features obviously)
WinCustomize Forums
You need to set TileLeft = 1 for that. Skinstudio does not make those options obvious enough and I think thats something we need to change.
Skinstudio will accept .PNG files and autoconvert them to TGA files for you so there is no need for WB to support them.
Changing the logoff/shutdown dialog text may not be easy to achieve. We will look into it, but I know its unlikely to be something simple to change.
paxx: more flexible in what way?
Vertically or horizontally?
Now that WindowBlinds 4.0 for XP has been released and appears to be a nice solid base for us to build on, we would like some feedback from skin authors about what you would like to see added to WB 4. We are aware of a demand for toolwindow skinning in UIS2 and MDI controls in UIS1, but would like to know what other features you would be interested in having in WB. You can also report any bugs in how WB draws things if you wish (not crashes - post them in our newsgroups, just p
What error do you get when opening spreadsheets? And which app do you use for those?
Its a problem with directory opus itself. It tries to skin its main window titlebar & so WB4 will stop its skinning of that window. You will notice the config dialogs skin perfectly and they have an additional titlebar button, so its clearly some leftover code in directory opus thats impacting the main window only. WB4 is very good at detecting such issues to prevent compatibility problems (such as skinning apps which self skin)
The version for Windows 9x/2000 will be released around the beginning of summer. We have said this is the case for some time now. The version for XP was completed first as XP has a number of features which 2000 and 9x do not have.
Explorer bitmaps are not in WB 4 right now. They may reappear in WB 4.1.
WinCustomize Forums
Beta builds of most of stardock apps will have a timeout if they are pre x.0 builds. So builds leading up to a major release (WB 1.0, 2.0, 3.0 and 4.0) will expire but beta builds of minor releases (1.x, 2.x, 3.x, 4.x)will not. This has been the policy for a very long time. We do this as the builds leading up to a major release may have major bugs and we do not want people to be using older builds and then reporting issues which have been fixed a long time ago. An OD
Frugus: Can you post screenshots of the corrupted buttons in the stardock newsgroups so we can look into it. The crash of ObjectBar may have been unrelated to WB.
Delicious: Thats an issue thats not been reported to us as far as I know. Are you sure you are not using Webblinds rather than WB? If not, then please post on the newsgroups (news.stardock.com) and provide screenshots of the problem.
JamMeister33: Please report any crashes you had with the alpha as we will not know about your problems if you do not report them to us.
They still seem to be including 34 skins in their downloads http://www.link-rank.com/download.htm I suspect stardock may be having a word with them on monday regarding some interesting similarities we noticed when we tried their skin builder. Are they also going to contact everyone they have sold their library to, and tell them that those skins cannot be used in their applications? Otherwise you may find a number of apps appearing which use the skins without knowing t
DavidK: WB4 does have an option to allow you to pick a shellstyle from a different skin. Its on the same dialog as the option to pick a taskbar & startpanel from another skin.
Its a bug in the skin not in WB4. All the skin styles apart from the original short titlebar version are missing a line to tell WB about the shellstyles which is why they revert to the luna look instead.
Sounds like its in an exclusion list for some reason. It should skin it as no changes to 3.9a would have impacted that.
Cleartype uses a lot of CPU and thats why its slower to paint. This is normal and happens without WB too.
You're about to visit an external site:
Sign up here to get the latest news, updates, and special offers delivered directly to your inbox.
