Sounds like you have been tweaking your drivers and have enabled stretching acceleration in the registry (or via an app like RageTweak) There are serious bugs in the stretching and this results in black parts where a stretch would occur. The registry key is called DisableDrvStretchBlt I think and should be set to 1 (or deleted from the registry totally as the default is off)
The shareware version of WB does not skin the scrollbars, tabs & progress bars at all. The menu skinning will disable itself after 30days. Did you perhaps have a previous install of WB which occured 30 days ago?
It mentions the drivers because they really are causing transition effects to crawl on nvidia cards. We felt it was wise to inform the user so they didn't start to blame stardock for a driver issue. Currently nvidia have not released any drivers which resolve this issue, but we hope they will do so soon (they are aware of the issue)
paxx: What graphics cards do your machines have?
It all depends on your graphics card. If it supports the right apis when it will work fine, but if it has no support then your CPU is used and thats many times slower. There is a performance advice page in WindowFX 2 which tells you if your card supports the apis or not.
craeonics: An early WB had a similar effect, but the WindowFX 2 effect is going to look nicer (thanks to most people having better cpus)
You have to remember the next version of Windows is not due until late 2003/2004.
Porting from a screenshot is harder than just using the original source graphics included in the skin directory. Anything that makes it harder seems like a good thing given the number of rips that have occured over the past 6 months.
You may be glad to know that we are working on a method of making skin rips from WB skins much more difficult. Obviously it will be optional, but I hope it will reduce the number of ports without permission and help protect the skin authors rights. grayhaze: Making ports now might just give them the impression that they can threaten to port skins and then they will get high quality ports made. I.e. exactly what they want.
It sounds like a corrupt skin is in your WB dir and thats what is causing the crashes. I would also suggest uninstalling WB, deleting all files in your WB dir (in case any are left over) and perhaps removing all WBD files (in the skin dirs) Then reinstall 3.3 and it should all be happy again.
If you are having problems then delete all WBD files in your skin directories. 3.2 seems to be accepting 3.1 WBD files and then getting upset about it. As for ObjectBar issues : its probably an issue in the OB WB skin loading system and not directly related to a new WB build.
4 pixels are automatically cut on each border with a WB skin as this is how windows normally work when they are maximized (look at a normal window & watch what occurs. Notice there are no left, right or bottom edges visible? and that the top border has lost its sizing edge) The skin author can change this in their own skin if they want via the MaxBorderCut Values. A user can force all the borders to show using the SizeLimit setting, but this is not the default as it would was
Chroma is an old app which I think is not in development anymore. Or at least its going slowly. Certainly their web site has not been updated since september 2000 and that was about their server HD crashing. The latest version is 1.1 which was released at the end of August 2000. A bit before WindowBlinds 2 was released.
I think someone should take a VERY close look at the HTML this site sends out. Just visiting 2 skin sections and looking at the first page only and then visiting the message board resulted in over 200k being downloaded. This is with pictures disabled so that did not have impact the results. In fact in the last 5 mins I have had 0.5 MB of traffic from this site (all HTML - no pictures), yet I have not actually downloaded any skins. All I did was look at the first pag
WinCustomize Forums
JoeUser Forums