bigmuscle

Preview version for Win10 TP (64-bit only) has been uploaded to the testers' profiles (if some of the testers don't see the link there, contact me again. Some of you didn't post me your e-mail address at all). Blur effect and almost all features should be fully working. It is not possible to customize colours for inactive frames yet and I don't reimplement this feature now. The part behind it changed a lot in Win10's DWM and I still see there a place for other changes, so it makes no sense to reimplement it now before Win10 RTM is released. Normally install it using the Task Scheduler script available in the website's guide and generate new key if needed (I added two additional keys for every tester so use them). Do not report bugs one by one (except of really fatal bugs), just write them down and report them all at once e.g. after several days.

Sure, it crashes if you don't respect the guide which I wrote.

Does any of the testers have 32bit version of Win10 TP?

Accent is the effect of the color with full transparency, e.g. default state of taskbar in Win8. The testing is for "users who provided the feedback during the previous development stages" only. I hope that everyone knows who they are.

Ok, I am almost ready. The current state is that Aero Glass for Win10 (let's use this working title for now) is working. Currently it just does not accept the transparency level set via Control Panel (or registry), because Win10's DWM does not provide this information to the renderer at all. I will distribute the preview version to the testers during the next week as a separate Win10 version. Later, it will merged with Win8.1 version and distributed to the testers again. If it works correctly, I will release it to the public then. It will still come under the name "Aero Glass for Win8.1 ver1.2.6" (there will be one DLL only for both systems) and we will see what happens when Windows 10 RTM is released - maybe it will be enough to have one version only (so we will create some universal name), maybe the changes will be so complicated that separate version will be needed. So... if any of the users who provided the feedback during the previous development stages are interested in the testing, write me PM with your e-mail (under which you are registered on my website). Please, users who just registered here, this testing is not for you. Also, do not register in this forum in hope that you will be the tester. Only the serious feedback is needed and many users from this forum already provided it before. I just don't remember all of them. Also, don't worry that I don't answer your PM immediately, I will just change the bit in your profile to the tester and you can download it there when it is available. -------- Meanwhile, I created a small utility which can alter blur (Win7-8.1) and accent (Win8-10) on any window. You can download it here: http://glass8.eu/stuff/EnableBlur.7z The usage is: EnableBlur.exe [hwnd | name | class] [<window handle> | <window name> | <window class name>] [blur | accent] [<true/false when blur>|<number 0-4 when accent>]For example, to disable accent and enable blur on the taskbar, use: EnableBlur.exe class Shell_TrayWnd accent 0EnableBlur.exe class Shell_TrayWnd blur trueEnjoy!

We are surely directing to situation where "Aero Glass for Win8.x" will not be valid name. Any ideas how to tag it properly when Aero Glass for Win10 is available? There is big probability that Win8.1 and Win10 versions will be merged into one release, because there are only minor changes in Win10's DWM.

No, it is because all your monitors are connected to the same video adapter, so DWM creates only one large render target for them (as max(width) x max(height)). When having more adapters, each must be handled separately. I will probably make some kind of garbage collector -> don't release resources on device/resolution change, but only create new one and release unused resources later (e.g. if no glass rendering has been asked for 5 minutes or something like that). This can make memory usage spike when someone changes devices/resolution too often, but I think this is very rare case.

I'm aware of this issue. There is a procedure when rendering blur effect and Direct2D device (or resolution) is different from last rendering than all device-dependent stuff (buffers etc.) are destroyed and reinitialized for the new device/resolution. This is done to avoid memory leak when device changes. But it causes problem when rendering by more devices simultaneously. I don't have correct solution yet.

Just one small thing: The picture was made as a quick preview how it can look in Win10. It is not usable at all, it may look good in the picture but it does not in reality. I doubt that you want Aero Glass that crashes every minute, accumulates dirt around the glass regions, loses the transparency very often and you cannot set anything. So if anyone wants to register to this forum just to demand for this version, he is losing his time and I will completely ignore such posts. When the preview version is ready, it will be distributed to the selected testers which probably happens when next preview of Win10 is released, not earlier. So again, do not ask for Aero Glass for Win10, do not ask if you can be the tester. All up-to-date information can be found here: http://www.glass8.eu/win_future.html

The first try...

so who are those "selected" users? Mostly the users who were active and provided useful feedback during the previous development stages. No sense to distribute the preview version somewhere else, because other users would only complain that it displays the debugging window etc.

From my first observation: there are only small changes in DWM. The main problem is that MS ripped out the last remainders of glass stuff which mainly means renamed functions. Thus, it currently does not work although you have symbols, because e.g. function DrawGlass is not there (it has been changed to DrawGeometry)... Currently, it should be possible to use my Aero Glass in Win10 to change atlas file only.

Maybe because it is Aero Glass for Win8 and not for Win10? Maybe dbghelp.dll+symsrv.dll is not compatible with Win10? There can be million answers why it does not work correctly on preview version of OS ;-)

It is simple, don't use atlas which is not compatible with system theme... + of course, the symbols.

My quick guess is that it uses the graphic card where your display is connected to

Aero Glass cannot influence this. This is only rendering extension which uses Direct2D device which has already been created by DWM.

It just modifies the installed files'/folder's permission so they can be accessed by DWM only and nobody can change it without admin privileges.

could you provide debug.log?

Good, solution to your problem is pretty simple - update to the latest version of Aero Glass.

I don't use OS X so I don't know what you mean.

Do you use default Win8 theme? I can't see anything wrong with your Aero Glass settings thus it must be something with your theme. Could you try plaing with GUI application (http://glass8.eu/stuff/gui.7z) to see whether some settings fixes the problem?

cyperbg: it looks like some application is modifying your settings. Could you share screenshots of registry editor displaying HKCU\SOFTWARE\Microsoft\Windows\DWM and HKLM\SOFTWARE\Microsoft\Windows\DWM keys at the time it is fully transparent (so before you change the theme).

I decided to wait for Windows 9 Technical Preview which is coming soon. If only minor change (or none) is needed to make it work there, I will update it and release. If large change is needed, I will release it unmodified and will make separate Win9 version then. Then main reason for delay is that the last Win update changed function pattern more than expected (thus DWM incompatible message) and I did not find a correct way to correctly fix it yet.

I'm not sure. If I remember correctly, it contains computer name and OS version only. Sure, it has already been fixed. I deleted wrong keys and you can generate the correct one.

Could you upload some of these minidumps?