bigmuscle

Build #639, 64 bit Designed for Windows 10 build 14393 Fixed DLL injection when system boots up too fast Fixed optimization of dirty regions Changed the way how it deals with colorization settings: * AccentColor (DWORD 0xFFBBGGRR) - color of active window frame * AccentColorInactive (DWORD 0xFFBBGGRR) - color of inactive window frame * GlassOpacity (DWORD, default: 68) - amount of glass opacity (0-100) or amount of blur blend with the background (10-100, see following settings) * EnableBlurBlend (DWORD 0 or 1) - 0 (default) means that blurred background is just overlaid with the AccentColor using the specified opacity; 1 means that the AccentColor is blended together with the background color using the specified opacity (the main difference is just the formula for putting blur and AccentColor together) Old ColorizationXXX settings values are ignored, because Win10 build 14393 always reset them to default under certain circumstances. I also think that those old ColorizationBalances and Afterglows are not needed anymore. There still can appear some random glitches. I currently do not know the cause but I would like to know if they appear often or they are very rare. If you have some other decision how to deal the colorization settings, you can put it here. http://glass8.eu/win_future.html

I know what you mean but you could select the better form of saying. You could put it as some decision or feature request and not just saying that I am obligated to do it. Because I am not. Aero Glass v1.4.5 is explicitely said to be designed only for builds up to 10586 and the incompatibility with future Windows version is even explicitely written on the website. If user install some low-level advanced software and then he installs incompatible OS, it is only his responsibility when it stops working and not mine. On the other side, since AG build 631, when DWM crashes several times in very short time, it will stop DLL injection completely.

Then please, do not use it, or just accept that this topic is about experimental builds and NOT about forcing me that I have some obligations.

MrGRiM: I removed your post, because I don't see any sense in it except of creating another neverending flamewar "I donated, I have rights, you have obligations". My simple answer is - no, I have no obligations, I will always develop my software as I want. This topic is about experimental builds testing and any other off-topic posts will be removed.

I just remembered that you probably still use that experimental "blur-blending" feature which uses ColorizationBlurBalance registry value to blend blur effect with the background. WinRS1 seems to revert ColorizationBlurBalance settings to 1 on every startup, so the blur effect will be almost invisible then. I do recommend to disable this experimental feature.

InvicTech: http://glass8.eu/guide.html

Glitches bug found and fixed. btw, this topic is about build for Win10 14393, posts about other windows builds will be deleted.

I finally found a cause for this problem. It will be fixed in next build. Unfortunately, this bug is not AeroGlass related. It appears without it. I found that it replaces ColorizationColor with AccentColor randomly. The only possible workaround (from my side) would be to create separate registry settings for transparency. Nope, it is not task for my Aero Glass. I'm aware of random glitches but they are very rare so it is hard to find the problem. It would be nice to track the exact steps to reproduce the problem.

MrGRiM: AeroGlass reads the colorization values from registry. The amount of transparency is got from I checked the old Colorization Control Panel and regardless what I set at Intensity slider, it always stores 0xFFbbggrr to registry. In pre-RS1 builds, it stored 0xAA according to the intensity. That's why it always uses the same value for transparency. So you cannot use that old control panel anymore but you must edit the registry values manually. NeolC: no problem here with auto-startup, no delay set, load "At system startup" enabled... as to colors, do yo have "Autocolorize according to background" enabled? I noticed that this settings resets stores zero transparency to registry and thus the frame will be completely transparent on startup. (and opening UAC dialogbox changes the transparency to higher value... funny)

Because there is no ModernFrame for RS1...

I'm aware of this. However, there is nothing to do, because this seems to be change/bug in RS1. The slider just does not change the registry values as before. I also noticed interesting thing - if you open some app with admin rights (= UAC box displays), the transparency will return to normal. But this is nothing I could change.

These builds are not intended for normal usage, they are just builds of my current working state. They may or may not work. They may contain features which may or may not be pushed in the final release. If you don't know how to install it then do NOT ask, because these builds are intended for very advanced users only which should already be familiar with the installation procedure. These are DEBUG builds only, they display watermark, they display debugging console and they display debug warning on startup. They may require debugging symbols for proper function. Do NOT use them if you do NOT want this or you cannot accept that these builds are experimental only. ------ Build #631, 64 bit Designed for Windows 10 build 14393 The main intention of this build is to test stability and various multi-monitor setups. Build #639, 64 bit Designed for Windows 10 build 14393 Fixed DLL injection when system boots up too fast Fixed optimization of dirty regions Changed the way how it deals with colorization settings: * AccentColor (DWORD 0xFFBBGGRR) - color of active window frame * AccentColorInactive (DWORD 0xFFBBGGRR) - color of inactive window frame * GlassOpacity (DWORD, default: 68) - amount of glass opacity (0-100) or amount of blur blend with the background (10-100, see following settings) * EnableBlurBlend (DWORD 0 or 1) - 0 (default) means that blurred background is just overlaid with the AccentColor using the specified opacity; 1 means that the AccentColor is blended together with the background color using the specified opacity (the main difference is just the formula for putting blur and AccentColor together) Old ColorizationXXX settings values are ignored, because Win10 build 14393 always reset them to default under certain circumstances. There still can appear some random rare glitches. Build #652, 64 bit Designed for Windows 10 build 14393 Fixed optimization of overlapped dirty regions Fixed data sharing between more drawings in one pass Includes new experimental ModernFrame.dll Build #668, 64 bit Designed for Windows 10 build 14393 Fixed occlusion management for overlapped dirty regions Build #669 - Pre-release, 64 bit Designed for Windows 10 build 14393 Same as #668 but compiled as release build Requires sign in to your profile http://glass8.eu/beta

There is no magic in it. Just a standard API for (unsigned int i = 1; i < iMaxPart; ++i) { RECT rc = { 0 }; if (GetThemeRect(hTheme, i, 0, TMT_ATLASRECT, &rc) == S_OK) { fprintf(f, "%u;0;8002=%u,%u,%u,%u\n", i, rc.left, rc.top, rc.right, rc.bottom); } }

Packing symbols with installer makes totally no sense and it is against the principle of the symbols.

Aero Glass automatically tries to download required symbol files if donation key is present in Aero Glass folder. However, as someone already stated in this forum, Microsoft servers sometimes fail and symbols downloading does not work correctly (not only in Aero Glass but it does not work regardless the used way). If this happen, I recomment to delete download.error file in Symbols folder and just try again. Anyway, code 0x8 is not important - it only means that inactive frames colorization will not work, but Aero Glass effect itself is not affected at all.

If you cannot login, send me your e-mail via PM. Sometimes, the e-mail does not come, because user's mail server rejects it but the login is still possible.

Just briefly... my current implementation works correctly in the latest builds. However, there are still some glitches that need to be fixed.

Still having the problem? I see other donations are processed correctly.

I would not say "blocked". Actually, the real problem is that TH2 added new elements into theme - mostly titlebar buttons separately for dark/light colors. And if your theme does not contain these new elements, it will not load at all - it means that you need specific TH2 theme and any pre-TH2 theme will not work.

Does it generate minidump file in Aero Glass folder? If yes, please upload it and I'll check who the originator of the crash is.

I think it is question to Opera developers ;-)

And are you sure that you even read this topic? http://www.msfn.org/board/topic/173139-read-first/

Please be patient, it takes sometimes longer timer to process. P.S. Before donation, you had to agree the conditions where it is written "PayPal mail box is not monitored thus you will NOT get any answer if you mail to it." ;-)

Sorry for not responding. I found a bug in dirty rectangles which can cause unpredictable behaviour on Win10 (and crash on WinRS1) and I'm working on it, but it seems to be a bit complicated.

You cannot use Aero Glass with WindowBlinds. Aero Glass is extension for DWM rendering, but WB disables DWM D3D rendering on windows and replaces it with its own GDI routines.