WindowBlinds 10 beta is available for Object Desktop members.
More info about that here: https://forums.stardock.com/474045
Please use this thread for discussion about the beta and reporting of any issues you might come across.
WB v10.0.1 update:
I found a fix/workaround for my problem with Chrome... My symptom was that I had an invisible/unskinned titlebar in Chrome, the rest of the window frame being skinned ok.
In Chrome advanced settings there is an option "use hardware acceleration when available" which I had ticked. When I unticked it and restarted chrome, my titlebar was skinned! Yay! This might point to a driver issue on my laptop I guess, although it says that my driver is up to date (Intel HD Graphics, onboard graphics chip...).
I don't care. It's working now, so I'll see how it goes.
Thanks for your continued work on this Neil...
What does DXDiag say for supported DX version and DDI?
Some images doesn't show. Like the Branding in Control panel. There's a black background image in Branding and sidebar, but usually it doesn't show at all. Once in a while maybe 2 out of 10 reboots it shows. Been checking the the skin/image in Skinstudio and the pic is there.
i have buy windowsBlind 8, but when i upgrade to windows 10, windowBLind 10 just for object Desktop, not for individual purchase windowBlind, can i get windowBlind 10 for my account ?
Not yet, as currently Windowblinds 10 is in Beta and thus only available to Object Desktop Subscribers.
Currently your options are to purchase an OD Subscription and access the Beta program, or wait for the general release...
Hi,
i have installed Windows Blinds Beta 10.0.2 (Beta 5) on Windows 10.1511 Build 10586.36) 64Bit (German Language)
The Problem is, after Install & reboot Window Blinds dosn't come up.
I have to start ist manually from the Startmenu.
When i do that, i can select a skin, but applying it takes very long (much longer then applying a skin with Window Blinds 8 under Windows 8.1)
The Screen turns grey, the Stardock Logo is visibly but after a long Time the Screen turns back to normal ans no skin is applied.
I read thrue the last 9 Pages and found out that several other people hav the same problem.
Could that be a Problem with Windows 10 Threshold 2 update (10.1511) ?
Or did anyone find a solution to this issue?
EDIT: Some more Information:
I had Window Blinds 8 installed on Windows 8.1
I Uninstalled an deactivated it before i did the update to Windows 10
In November i updated to Windows 10.1511
Now i installed the Beta, activated it and getting the problem described above.
The Beta still finds my installed Skins from Windows 8.1
The only anti virus Software is the windows Defender
Please contact us in support so we may assist you: https://esupport.stardock.com/index.php?/Tickets/Submit
Either WindowBlinds10, or Start10 has a bug.
I get no mouseover effect on any skin on the start button.
Latest versions of both apps. Latest full release of Win10.
Yup, start button states on Windows 10 do not work correctly at all, on any skin, even the ones that come with WB10. However, if you go in and set some animation rate settings on the button in SKS10, it works for some reason. Evidently a major bug in something, either WB10 or Start 10 for sure.
Don't know if it's a bug or the nature of the beasts -
(Win10 64bit) - None of the "User Icon Frames" or "User Icon Backgrounds" defined in the WB's are displaying around/behind the Start Menu User Icons, regardless of which Start10 style is selected (Win7/Modern/Win10). Consistently get a (rather nice) semi-transparent light frame on the Win7 and Modern styles.
Start button glows seem a little funky. Seems like if the combined glow and button is small enough they will get combined and display completely within the taskbar (e.g. Gloss Burgundy). If the combined images are too large the glow image will show on the tasbar and the start button itself will be pushed off the bottom (e.g., Assimilation V3).
(btw I'm really liking the Start10/WindowBlinds combination )
Quite frankly, I still fail to be impressed seeing how the damn thing doesn't even run on my machine. Not really an issue though as I still prefer Win 7 as a main OS so the prior version of WB still serves me well.
I just noticed that. No mouseover effect on the start button plus no effect when clicking on it. Running Alpha Nebula skin. Previous one was Naked Noir and on that one the effect on clicking the start button was there but no mouseover. Thanks RnD for making me look.
This would appear to be something specific to your computer.
Assuming you did a clean install the most likely explanation is some sort of Antivirus or antimalware app which is helpfully breaking things without telling you.
ESET is a particular offender.
This would appear to be something specific to your computer.Assuming you did a clean install the most likely explanation is some sort of Antivirus or antimalware app which is helpfully breaking things without telling you.ESET is a particular offender.
Happy to report.. i haven't found a single bug here.. superb job!
Then again.. It's also not installed
Merry Christmas!
Uvah, I just tried Alpha Nebula and have the same issue with it. However, I am running older W7 skins with no problem at all. I skipped W8 altogether.
On 8.1 I'm running Alpha Nebula with Start8 installed and the mouseover effect is there. In fact it works on all the skins. Just not on WB10, have Start10 on Win10.
This reply is so you. Otherwise, it wouldn't be funny. But is sorta is.
I am having a problem getting the "Per Application" to work.
Windows 10 Pro (10586.th2_release.151121-2308)WindowBlinds 10 BETA (005 - Windows 10 Edition) - 64 bit OS
I set WB to ignore CrashPlan & Spotify, however it is still trying to skin them. They are having all kinds of interesting text issues (mostly just the same color as the background) in CrashPlan because of it. I have alway excluded CrashPlan because of this. The minimise, maximise and close buttons have random problems in spotify.
The colour scheme is a global thing which probably explains the text colour issue. Some apps hardcode the background colour but then pickup the OS system colour for foreground text which leads to problems if it is not as they expected. Likewise the reverse. Those apps are unfortunately at fault and they would need to fix that at their end.
What sort of random problems are you having with spotify titlebar buttons?
when is the beta out for all of us
cant wait lol
tinbin
As Jafo would say .... by the time it's 'for all of us' it will be out of beta
I realize this has been requested in earlier versions of WindowBlinds, but I haven't seen it here, so I ask again:
Could we please have the option to move the default directory for skins like we can in Deskscapes, etc.?
With todays SSDs being small, it would sure be handy. It can be done via registry hack, and I have done it, it works. But the hack must be redone with every WB update, so why not just give us the option?
Please........
Should Firefox be skinned with WindowBlinds 10.02?
I am running Windows 10 build 10586. I upgraded from Windows 7 a few days ago.After the upgrade, I installed WindowBlinds 10, beta, version 10.02. I am using the theme Lantana, one of the default themes that shipped with WindowBlinds. I have rebooted a couple of times since installing WindowBlinds, so that's not a problem.I am using Firefox 43.0.2, the current release version, and this should be the 32bit version, since I have not yet gone hunting for the 64bit version.I have reloaded Firefox with all addons disabled, via the help menu. This made no difference, still no skinning.I then used the Windows key + R (run) dialog to run the command "firefox.exe -P" and launched Firefox with a brand new, blank profile, as if it had never been run before. Still no sign of any skinning by WindowBlinds.I am also running Start 10, and launching Firefox this way.There are no special rules in WindowBlinds for Firefox, and so far every other program is being skinned. Thunderbird 38.5 is being skinned correctly.Should I expect Firefox to be skinned under Windows 10 with WindowBlinds 10? Can anyone confirm this works?
Firefox on Windows 10 draws its own titlebars which look like the Windows 10 ones but for reasons best known to them are not the standard ones. This means it conflicted with us trying to draw our own as they still have their fake buttons drawing and accepting mouse clicks. Unfortunately the only solution was to exclude those windows.
Complaints should be directed to the Firefox developers as I am struggling to see why they did that vs using the native OS titlebars as every other app has done.
There are many great features available to you once you register, including:
Sign in or Create Account
