Quoting essorant,

reply 201

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?

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 ?

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

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.

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  )

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.

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. 

Quoting vStyler,

reply 215

Happy to report.. i haven't found a single bug here.. superb job!

 

Then again.. It's also not installed

 

Merry Christmas!

This reply is so you. Otherwise, it wouldn't be funny. But is sorta is.

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?

As Jafo would say .... by the time it's 'for all of us' it will be out of beta

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?