bigmuscle

AERO GLASS for Win8 RC0 What's new? * correctly adjust colorization settings to generate glass safety zone --> this should remove most of artifacts caused by not reducing occlusion rectangles by blur radius * correctly choose whether to fill surface by color or to blur its background * frame colors respect theme opacity settings * fixed incompatibility on some dwmcore.dll versions * workaround for crash on settings reload * fixed colorization algorithm in 32-bit https://developer.berlios.de/project/showfiles.php?group_id=13124

Please, dont react to those complaining about message box. I see absolutely no sense to register to this forum just to complain about message box that has been discussed million-times in this thread.

I'm aware of this crash, I know what it is caused by but I cannot reproduce it :}The reason is that dwm.exe process is running under different user (Desktop Window Manager\DWM-1,2...) privileges which does not have access to your profile. So when DWM needs to read some user's settings, it must ask some remote process to give the registry key handle. I catch this registry handle and store it so I can read user's settings (mostly inactive frame colorization). But when remote side destroys this handle and my library wants to use it then it will crash. No solution for it yet

Does anybody has access to 32-bit version of Windows 8 Release Preview and could send me (via PM) file C:\Windows\System32\uDWM.dll ? (32-bit RP only!)

Fine except it lacked support for multiple monitors, I suppose. Multimonitor support after 0.7 is just the least what was added there. The biggest change is that 0.7 was using that old layered windows hack which degraded performance a lot and made a lot of applications not to work. It also contained many memory leaks and security bugs which has been fixed later.

Clicking the popup dialog is much easier and takes much less time than registering in this forum...

Windows version perhaps? I have x64 pro, downloaded a day or two after release, fully upgraded I think. I applied the reg key multiple times because of that error, but yeah, that shouldn't have done anything. Not sure what else it would be either. What was it supposed to do? Nothing special, it should change the color palette (color + name + preview bitmap).

It is for me. Without it it just makes windows transperent. It is very interesting, because there is no code which makes the windows transparent. Such code was present in old version but it does not exist anymore.

So script is imported correctly. I don't know why swatches bitmaps has not been replaced correctly :-(

Ok, something is wrong. When you click on some color, is the frame color changed to that one which you selected or to different one? And when you hover color swatches, does it display color name or just plain "Color #" ?

Post the screenshot of your Colors control panel.

ok, I hope you can find it Yeah, I found it. There are two functions responsible for saying whether the component contains glass and whether the glass safety zone should be added. I can force them to return always true (they always return false on Win8 RTM), but I think it should be better to handle it correctly.

There is a problem that two internal DWM functions have the same code in your dwmcore.dll version so it is difficult to recognize the correct one. Maybe I will fix it later but not now because native blur rendering is not so important.

Nothing interesting if the version I sent you works

When using explorer7 then taskbar is drawn with inactive color. I'll fix it later.

check my PM

The glitches are normally caused by blurring the clipped region when the pixels outside of the clipped region are not available. It means that DWM wants to draw part of window, so it sends underlying texture - e.g. wallpaper - for this part only. Since blur effect is generated from the neighboring pixels this will result in glitches on the edge of the clipped region. However, my aero glass utility has a workaround for this which should work in the majority of the cases - and it even seems to be working correctly for the most of users. The only problem which is not solved is when you place more frames closer and move another frame over them. But such glitches are not so horrible and they are almost unnoticeable. I'm going to fix this problem completely but I cannot say when this happen because I need to find part of DWM code which is responsible for this.

That glow is theme thing, because RP theme has glow everywhere (even for Explorer and Wordpad).

drakenabarion: your settings seem to be correct, but could you provide your theme resource? Do the glitches appear always, i.e. anytime you drag one window over another or only when new window is opened over existing frame?

Please, send me your dwmcore.dll in PM. Check your PM, I've sent the file. Fine, I find a small problem which can cause that glass can fail under certain versions of dwmcore.dll. The weird thing is that even you have same version 6.2.9200.16384, the file is different than mine. I'm working on a fix.

Don't you have StartIsBack or something which alters taskbar transparency settings? If it is more colorized than it seems that accent has not been disabled for taskbar but my utility should disable it (or better, it forbids enabling it) Should read properly before asking:

Please, send me your dwmcore.dll in PM. It is not about permission and owner of the registry script but of the registry branch where the file is imported to. Normally, user don't have write privilege to the registry key and this privilege can be changed only after taking ownership of the registry key. About swatches... it's the palette of the colors which you see in the colors control panel. The colors in the script better match to the transparency effect and as a bonus it even changes the color preview to "glassy" look. And about glitches... don't use native blur rendering.

AERO GLASS for Win8 BETA3 Ok, here it is. What's new? * completely removed layered windows hack * fixed glass on the secondary taskbar * many code fixes and refactoring * almost all low-level stuff (see beta 2 changelog) should work regardless the used DLL versions and even on 32-bit --> this probably still needs some coding --> works until MS changes the internal DWM functions --> if something is wrong, message about DLL incompatibility will pop up * implemented that color swatches in control panel can be loaded from external DLL --> registry script which changes default swatches to Win8 RP (more glass-friendly) is attached --> backup the original registry key before importing !!! --> you will probably need to change the owner and permission of the registry branch --> DO NOT do it if you are not advanced user!!! --> you will be unable to change frame color if you don't use AeroGlass utility after importing this registry key * fixed glass on surface render targets --> glass won't work if one side of your screen resolution is less than 200 pixels https://developer.berlios.de/project/showfiles.php?group_id=13124

There is no 0.85 version, you probably mean that debug build which was intended for testing surface render target only. The other things in it are completely broken so it is normal that you get message boxes about incompatibility. And yes, inactive colour can be changed in HKCU\SOFTWARE\Microsoft\Windows\DWM using DWORD values ColorizationColorInactive, ColorizationColorBalanceInactive, ColorizationBlurBalanceInactive, ColorizationAfterglowInactive and ColorizationAfterglowBalanceInactive .

I see this as the bug in the theme and not in the aeroglass utility.