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.
Neil Banfield
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.
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.
Directory Opus attempts to skin its own titlebar & so WB automatically disables skinning on its main window. You will have to ask the authors of that app to stop doing that.
Actually its quite a bit more complex than that! It is a wonderful feature though and the forced colouring feature added to WB 3.4 improved it even more.
Post from Kyl deleted
WindowBlinds can skin the toolbar buttons background. In fact it has been able to do that since 3.0. I am not sure where people are getting the idea that WB cannot skin them as its 100% false.
I recommend not using nView as its very inefficient and seems to cause a lot of issues with a number of things.
The minimize issue has been fixed internally. It mostly occured with UIS1 skins too. The latest build of WindowFX on OD has an option to darken or not darken the skin when using lights.
moshi : As you say Illumination only feels quicker because it skins so little. And even then its actually slower if you benchmark it. As for the incompatible skins, I guess they are using per pixel alpha and not using magic pink in those areas too. WB on 9x does not currently support per pixel alpha, so it ignores that part. Perhaps that is something we need to implement on 9x (though with a performance hit obviously)
chichigirl46: In what way are WB3+ versions of WB not compatible with Windows 9x? If you are having issues then we want to know about them.