bigmuscle

yavordh: this is beyond the scope of DWM itself. If application (explorer in this case) calls DwmExtendFrameIntoClientArea then it could work. It could work even if you call it remotely but it is not work for DWM. To the others: Please, I'm asking you again, stay on-topic and don't discuss any theme-related things here. Make a separate topic for it but not here, it makes difficult to track any possible bug reports or questions which are related to this project.

I supersede all theme stuff for 2.0, then I could take a time and look whether it is possible to set caption offset (and change also other theme stuff) directly in DWM.

I guess that the position can be found in vertex buffer and thus it can be easily changed. The main problem is that it will absolute screen position (and not window position) thus it can be more complicated to compute the correct position relative to the window (you don't know the window position/size when text is being rendered etc.). I am not sure whether the final absolute position is computed by DWM or by some other component (themeui for example).

NoelC: Details are important at this phase. However, it was already written about inactive windows - either use better theme or play with ColorizationColorInactive and ColorizationColorBalanceInactive registry keys.

You can add more DLLs to this value separating them by space or comma.

aaah, I don't want you to upload the files, I just want to know their versions

I don't have this problem here. File Explorer and Wordpad, both have the glow behind the window title here.

Yes, it is general question. I'm implementing certain low-level functionality/fix which requires exact UDWM/DWMCore versions. So need to know if it is same everywhere or more different versions exist.

Please, could you post here the file version of your C:\Windows\System32\UDWM.dll and dwmcore.dll? And state if it is 32-bit or 64-bit.

It's not probably anywhere, just because Win8 does not support it at all - you must use tweak in my utility to apply rounded corners. Else... even if you modify theme texture, Win8 will still colorize whole rectangular area and even if you force Win8 not to colorize it (e.g. color is hardcoded in theme), it won't redraw that missing part of the corner (because the occlusion management will still take whole rectangle).

This is not as simple as it looks :-) a) C:\Windows does not seem to be a good place for DLL, because dwm.exe is run under standard privileges and thus it has not write access to this location. It results that it won't be able to generate debug logs. B) AppInit_DLLs key causes that the DLL is loaded into every process which is linked with USER32.DLL. Thus simple killing dwm.exe does not unload the library from the memory but only from the address space of the DWM process.

I still don't understand it. There is no way to reload DWMGlass64.dll, so I really miss what AGTweaker does. Do you use StartIsBack or any special settings? AeroGlass injects into explorer.exe and denies any request to change taskbar blur/transparency settings. Instead it forces blur to be enabled and taskbar to be completely transparent (because blurring maintains the colorization itself). So it seems that something override the blur settings.

If you want to use GlassTransparency settings, don't forget that inactive frame colour will be overplaced with ColorizationColorInactive. Thus should play with this settings. I already posted the link to the theme which I use - it is Release Preview theme. Maybe I miss something here, but how do you run DWMGlass again via tweaker? This is not possible in 0.7, because the only option here is to start via AppInit_DLLs registry key.

D3D mode works the same way as it worked in Win7 so the only way to adjust the blur is the ColorizationBlurBalance settings. But yes, it does a bit different thing than extending blur radius as BlurDeviation in D2D does. You could try app such as AeroTuner to modify the native settings. To others, please don't discuss any theme-related things here, neither rounded border etc. I does not have anything to do with this piece of software.

yeah, I admit that colorization settings is a bit tricky because it is not documented anywhere. But you can get nice results by playing with it. Also, the current blur effect is not the final appearance. It should have much more blur but if I use the blur weights from Win8 RP, I don't get the same result as it should be. I need to play with it more...

MagicAndre1981: What do you mean by full glass? I don't see the point. In Direct3D mode you can get exactly the same look as in Direct2D mode by playing with the colorization settings. Or do I miss something?

Direct2D mode has absolutely no sense, it's additional layer which complicates everything. It must maintain many Direct2D objects, recreate buffers everytime you want to render blur effect etc. It is also 3x slower than Direct3D mode and not native at all. Also, at this time, Direct3D mode needs to be tested so there is no sense to keep Direct2D mode.

Amount of the blur can be controlled by ColorizationBlurBalance which is native DWM settings. I have not tried updating driver. I just tested disabling/re-enabling driver in Device Manager and it works correctly.

ok, nevermind, we could have this option too since next build will have Direct2D mode removed so it is better to have some way to disable blur effect

I must admit there is no HideBlur in my Win7 installation and neither DWM knows this value.

Sorry to say it, but there is one thing which always drives me crazy for the whole time of my experience with PC administration. I said many times that this piece of software is just a preview, alpha, beta or whatever which should be used by experienced users only. And also the preview-notification dialog is not there for fun. So if someone is not even able to read the instructions which registry keys to modify and randomly mixes values in registry and tries to set the registry values which should not be set at all, then he should not use this application until the final version is released. MagicAndre1981: yeah, higher CPU usage can be caused by layered windows thing. I'm working hard to fix this problem and remove layered windows completely :-)

Ah, I just noticed there can be problem if each display has different resolution because GetSystemMetrics returns size of the primary monitor only. Image my.ping adds caption glow only (not buttons) and you must restart dwm.exe after editing registry (or just change something int Personalize control panel).

There are two undocumented functions in dwmapi.dll - DwmpGetColorizationParameters and DwmpSetColorizationParameters. These can be used to read/write the correct values, because the public function DwmGetColorizationColor does not return the correct value.

The border edge (the black line in the image) is stored in theme sprite too together with the content of the border. There are several parts - 4 corners, 2 horizontal and 2 vertical segments. And all doubled - active and inactive border.

Yes, type REG_SZ with whole path to PNG file. I'm still working hard on finding correct solution for repainting of occlusion regions. Currently, I found a way of setting alpha channel directly for DWM visual objects. It works the same way as layered windows, just the WS_EX_LAYERED bit is not set so WPF and UAC windows transparency works correctly. The problem is that I can't decide which window I want to modify this way - so even desktop background is blended with transparency 0.9999 and it's not performance optimal at all.