bigmuscle

This build is not intended for working computer. If you don't know how to install it then don't use it.

!!! EXPERIMENTAL TESTING BUILD ONLY - DO NOT USE ON YOUR PRODUCTION ENVIRONMENT !!! This is a stability-testing debug build for 10240. It contains some internal changes, new features etc. but it is not fully finalized yet so I don't describe it now. The only intention is to test the stability now. (Win8-like atlas theme is distributed with it) http://glass8.eu Your donation does not turn any preview/alpha/beta/rc testing version into the full usable release without debugging means! !!! EXPERIMENTAL TESTING BUILD ONLY - DO NOT USE ON YOUR PRODUCTION ENVIRONMENT !!!

Hello, it is my own implementation.

Interesting, they must have changed it again.

Because this is development/debugging/testing version only. If you don't know how to install it, then you should not use it.

You can modify button height by setting CaptionWidth in registry (this value is used both for width and height). I don't know the conversion formula from this registry value, but it seems that resulted height is (CaptionWidth in px + 8) limited by title bar's height.

Motwera: yes, debug builds are intended for debugging/testing purposes only and not for using by common users.

I wouldn't trust Microsoft promises. They also promised that Win10 will be designed according to user's feedback and they have done completely opposite thing.

As I already said, Windows 10 is still under development and there are still changes in every DWM build so it makes no sense to hurry and tune Aero Glass for every build. Last Aero Glass debug version is designed for build 10130 and if somebody got it working on b10162, it is just by chance, completely random, nothing that you could influence.

Unfortunately, this won't be so easy because the instruction is placed in the middle of the bit extensive function so it is really difficult (almost impossible) to detect the exact memory location to patch on the fly..

Noel: I checked the default atlas and your atlas for FrameMargin = 10. In both cases, there is blur of 10 pixels in width. Then, with default atlas, it continues with 1px semi-transparent color followed by several pixels of shadow. With your atlas, there is 3px semi-transparent border and then the shadow. So it looks like the default atlas does not contain shadow at the correct place but rather in the area where you have that 3px border. There is also abnormality, that active frame has blur of 11 pixels in width (1px more) which makes this problem with your atlas (and also other atlases...). Quick solution: offset the side borders by one pixel and add 1px of shadow to the edge. Is this possible? EDIT: yes, I found it. It's not in 10130 but it is in 10162 - for inactive frame, the geometry is cut by 1 pixel (or logical pixel size if your DPI is not 96). --- About the inactive frame coloring, it seems that there is another Microsoft try to add more hardcoded values. Up to now, inactive frames were drawn with opacity specified in theme file. Build 10162 has this value hardcoded to 0.4. However, it is not hardcoded on all places, thus I see two different color shades on inactive frame (and it is visible with your atlas too).

I don't know if it is mistake or intention. I will surely check it, because I noticed more different things on inactive windows - e.g. different color shade is used on left and right part of the frame.

It does not seem to be related to FrameMargin but rather to used atlas file which is "incompatible" with current version of DWM. It probably makes inactive frames geometry one pixel smaller and it must be taken into account in atlas image.

Anyone still running build 10130 and could provide ApplicationFrame.dll, I forgot to back it up before upgrade. PM me, please - don't send in public. Got it, thanks.

Looks as though now they're drawing the caption buttons taller, relative to the title bar height. I really liked them shorter, so I've changed the graphics a little. I've had ZERO time to test this, but it might make the caption buttons a little less awkwardly positioned... Chances are I still need to move some things around, but here you go: Noel, were you able to change caption button height by some settings or is it only hack by making the button image smaller in the atlas? I'm asking because it seems that it accepts registry settings in "WindowMetrics\CaptionHeight" but it does not take the real value. It is probably (not exactly) double of used value and value "CaptionHeight" influences both height and weight. Value "CaptionWidth" seems to be ignored.

It is random. It even works on 10158 (except glass safety zone implementation) but it depends what data are stored in invalidly pointed memory. I actually don't know if there is some possibility to check that pointer is invalid and I should not inject my code. Currently, it does only "if(pData != NULL)".

Then this is the limitation which cannot be easily fixed. UxThemeSignatureBypass hooks DrawThemeTextEx to modify text parameters on window caption but it is not possible to differentiate if application calls this function for another texts.

do you use my UxThemeSignatureBypass ?

There is no native Aero Glass in Win10.

shelter: now try it without Aero Glass

Interesting, it must be some VMWare driver problem then. It happens even when Aero Glass is not running.

Could someone confirm me that it is not only me. That new taskbar blur feature in Win10 seems really unoptimized - moving the window beneath the taskbar is a bit jerky and dwm.exe CPU usage goes high.

According to your screenshot (only one console window on the taskbar), you have not installed it at all.

Why is still someone surprised when Aero Glass does not work on some unofficially leaked build ? daveo76: clear blur? What do you mean? Just without color? Just use Aero Glass GUI and set it as you need ;-)

I uploaded experimental debug version for the build 10130. It can be downloaded on my website.