All our testing shows it works perfectly for multiple user setups. If you still have a problem, uninstall WB totally and reinstall it.
Neil Banfield
scorpio-logic: WindowFX lights ARE turned on in that picture. Try enabling & disabling the option in WFX to see if that helps
You are not losing features as your old skins continue to work just as before. But the per pixel skins will not support the edge clip setting as to implement support for that involves a considerable amount of work for little gain. If you want to prevent windows from covering your docks & widgets when maximized, then you should not have been using screen clip settings in skins anyway. That setting was designed to allow the skin author to show slightly more or less of
There is a bug in firefox which can cause its content to jump around. This can happen with or without WindowBlinds.
theleader: The GT3 skin switcher built into the skin is not aware of changes made to WB5 and so it will not work with WB5. Kevison: The Outlook issue should be resolved in future builds. There is a minor colour scheme applying issue with the current builds which is making certain system colours turn black.
Looks like you turned on the WindowFX lights feature.
If an excluded window is skinning then most likely it is currently not responding. Not responding windows get skinned by explorer (it is complicated, but it is how XP does 'ghost windows' for non responding windows). So its not WB that makes it not responding, its becoming not responding which causes it to skin.
Can you install Smart Exception (free apps part of SDC) and then see if it logs anything about the crash. Also does the crash dialog have any details?
Koasati: Screen Edge Clip settings will not be provided for per pixel frames in WB5.
Products can also be activated by e-mail. Given that the products are activated when you download them, the site being down is unlikely to be a problem as it would have been down when you tried to download it anyway regardless of if it has activation or not.
Older Theme Manager builds are not aware of WindowBlinds 5 changes. There should be an update of Theme Manager to resolve this.
No, there will be a Wfx update to work with WB5
In no version of WB5 have per pixel titlebar skins supported a text background.
I believe your ThinkDesk 1 year subscription starts counting when ThinkDesk is officially released. So it hasn't started yet. There should be a new Keepsafe build and Multiplicity build coming soon.
The latest build had no changes to wallpaper support and the display properties desktop tab is not touched by WindowBlinds and never has been. Your Object Dock Plus issue sounds like a problem with Object Dock Plus, not WindowBlinds.
We believe the black area is caused by WB not correctly setting one of the system colours. This has been fixed for the next build. On the windowblinds button, this should be in display properties still. If it is not, run regsvr32 wbui.dll from the WB directory on 32 bit Windows OSes. On 64 bit OSes we currently have not updated the display properties UI but will be doing so before final release.
You should be able to run it under other user accounts. We certainly have in testing! Just run wbconfig to change the skin as normal.
WindowFX and all those other apps do constant transparency. The entire taskbar has one transparency level. If you set this to say 10% then the entire bar is 10% visible and the text would be unreadable. The WindowBlinds 5 feature is per pixel. This gives the skin author so much more control and the text, icons etc can remain fully visible. The side effect is it is not aware of windows under it.
Slow doing what?
The current WB 5 build on OD (4.95 beta) should handle multiple users just fine. Just open wbconfig to change skin.
Do you get any crash messages?
pinchecl: Maximized windows don't have visible left & right frames so thats why there is no per pixel on them I am unsure about your other issues. Per pixel doesn't support custom menubars, MDI images, text backgrounds etc, so if you are talking about that then thats perfectly normal for per pixel skins. Non per pixel skins should continue to work as they did with WB 4.6.
No it is not. The new WindowBlinds beta is out now, but the WindowFX one is still under development.
MP should bind to ALL active adapters (and thus IPs)
Multiplicity Standard only supports one secondary machine. So either on the left or on the right. Multiplicity Pro supports more secondary machines (upto 6 I believe)