sbkw1983

See attached picture. The color chosen is black for both the active window and the inactive window. I believe 'Color Balance' is the same thing as 'Color intensity' in Windows 7.

I assume you're talking about the registry entries located at [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\DWM] , yes? If yes: "glass color" aka 'ColorizationColor' = the color of an active window. "inactive glass color" aka 'ColorizationColorInactive = the color of an inactive window Did you read through the following link: http://glass8.eu/guide

Sure thing, timia! I'll definitely take a good look and keep you posted. Also, you're very welcome and I'm glad we talk alike :-) I gotta run for now - take care!

Gratitude for this! Much obliged!

Hey timia, I hope you are well. Just wanted to let you know that I purchased a key for Windows Style Builder / Vista Style Builder for 25 euros, and with the aid of Mr. Grim's patches (bless that man), I'm using the latest version (it says "1.5.6.3 - Beta Build") to aid in the border thickness query, as it also is something I've wanted to hopefully-address for the theme that I use as well. Just thought I'd let you know that I am indeed investing my time and resources into this. It's the perfectionist in me. Probably undiagnosed OCD as well, LOL. So, erm, I promise I'll keep you posted about the border thickness and so forth, unless you tell me to shut up, and then I'll shut up. Take care, bye for now :-)

You're very welcome. I suspect that there's a tree for the taskbar, and then another one for the start menu, and so forth. Or am I wrong? Either way, I'll know for sure soon enough.

Indeed, that's the one. I don't mean to sound arrogant, but how hard can it be to use? I'll find out this weekend. I have a fair amount of experience with Stardock's WindowBlinds' counterpart (SkinStudio). Hopefully it's relatively similar (point and click for the most part). One thing is for certain: I no longer use WindowBlinds. Don't get me wrong: I admire Stardock's attempts to code a skinning engine for multiple versions of Windows, but in the process, many of their better (master) skins increasingly suffer from bugs as a result of (mainly) deprecated features. They ought to to start over and focus solely on Windows 10 + keep it streamlined. Just my two cents.

Apologies to Aethelflaed for essentially repeating what he stated, nevertheless, I too would like to stress that the Settings window - as well as the latest version of Microsoft Office and UWP apps in general - are rendered differently compared to W32 apps. This is why they appear to be unaffected (or only partially affected) by AeroGlass and/or custom (third party) themes.

Hey timia. I believe that the borders in question can only be modified by way of editing Windows Visual Style Files - each of which, contain the *.msstyles file extension. In order to do so, the only software I know of which MIGHT be able to modify the borders in question is Windows Style Builder. I say 'MIGHT' because I'm not certain how compatible it is with Windows 10 in general. I'm going to purchase a license this weekend and go from there. I'll be sure to keep you posted.

BigMuscle, I just wanted to remind you that many of us are unconditionally grateful that you continue to update your software. Yes, the cumulative updates tend to throw a wrench in your schedule, however, I'm very glad that you haven't given up. Thanks for the update, and keep up the great work, cheers :-)

I sincerely apologize for taking so long to respond to your question, AdamW. I was away on business. Sadly, I missed much of the World Cup as well, but I digress. ---------------------------------------------------------------------------------------------- Regarding glass on Chrome, Blonk's post contains precisely that which I would have written for you, so thank you to Blonk :-) I also recommend that you might consider the following theme, which, is displayed in the included screenshot + linked below: https://chrome.google.com/webstore/detail/f2b-dark-electrique-neon/dpcngmlhjpglhbdbomhggfdjebkgaoap I happen to contend that it's good-looking enough to share with y'all :-) Anyways, have a great day everyone!

There was a new cumulative update for me from Build 17134.112 to 17134.137. 1) A new folder in 'C:\AeroGlass\symbols\dwmcore.pdb' needs to be created named as follows: D1149747277D9F7BA3C1C34E145203531 2) A new 'dwmcore.pdb' needs to be downloaded from the following link: http://msdl.microsoft.com/download/symbols/dwmcore.pdb/D1149747277D9F7BA3C1C34E145203531/dwmcore.pdb 3) The downloaded .BLOB file needs to be renamed 'dwmcore.pdb' and copied to the folder created in the first step. 4) Click the 'retry' button in the 'incompatibility' popup window and it should work.

Haha - well, God bless you for investing either way :-) Thank you!

Aye, their presence can indeed be rather vexatious, especially if it has been repetitive and you've got a lot of work to finish up. I certainly don't blame you for ditching the debug DLL. Admittedly, I too have done so in the past. At the same time, I'm really grateful that we have BigMuscle around to continue working on AeroGlass. And I'm confident he'll release version 1.5.9 soon enough :-)

You are a Platinum Sponsor after all. It was the least I could do, have a good day :-)