bigmuscle

Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.

Unfortunately, this cannot be fixed. Windows 10 renders the window frame and a top caption part separately, so edges are blurred together.

Please, be patient, of course, there is going to be the new version soon, bit I'm a bit busy in the current situation.

Hello, there is a small glitch in AG that needs to be fixed to support this update. However, when I run my testing machine, DWM.exe randomly crashes even without Aero Glass. Maybe it's connected to remote debugger. I don't know but it did not happen before.

There is no reason to create the same topics about things that have been discussed thousand times in this forum. Topic locked.

This is known problem and unfortunately I have no solution for it. The only workaround is to disable "Fast Startup" function in Win10 which is very buggy.

Then enable verbose logging and post your debug.log.

Delete c:\AeroGlass\symbols folder and restart your PC. If it does not help, then your Windows installation is broken.

Topic locked as it makes no sense to spam topic about years-old version with something that has already been discussed million-times.

https://glass8.eu/guide

It should take a few days maximally, but it takes a few hours mostly. It just depends how fast PayPal sends me notification about incoming payment, some notifications take longer than others although the payment is already marked as finished. I would check the spam folder at first, then I would check your PayPal details. I noticed that many of the "I can't login" complaints come from users who tries to fill in the login e-mail/zip that does not match their PayPal account.

Weird, I just reverted to the previous code where it should be working. However, I'm away from my working computer now and I cannot check before new year.

This will be fixed in the upcoming release.

It depends where there is some official way to initiate "go back" action. There is undocumented WinAPI message, but Microsoft changes the message ID with every new build. But I'm not even sure if it makes sense to maintain glass frame for UWP apps, because blur effect is already there.

I think it would be good to look properly at first (I already wrote in Firefox topic that moz-glass-win property works now only when WebRender is disabled) instead of posting off-topic stuff into unrelated topic.

And the text in the message box is written unintelligibly ?

Could you test with this build: http://glass8.eu/out/19h1_18362_1607_x64dbg.7z

The same happens on Opera. I guess it is because hardware acceleration is enabled on Windows 10 only thus compatibility mode disables it.

There are two settings (about:config ... gfx.webrender.all.qualified but the value needs to be changed directly in prefs.js) in FF67. If they are not present or set to "false", "moz-win-glass" value is accepted correctly. The problem is that these settings are reset back to "true" after several restarts.

I don't know Pale Moon but I guess it is just a port of old Firefox. The question is if the statement "there would be visual glitches on Windows 10 without custom caption bar drawing" is true why these glitches does not appear in any other application except browsers (+thunderbird) that try to imitate Chrome behaviour; why these glitches does not appear on any other DWM-based OS (WinVista, Win7, Win8, Win8.1 - where rendering is exactly same) and why these glitches did not appear in versions before adopting Chrome look. Maybe, we should highlight that this look does not correspond to Fluent design

Thanks for your report. Does it generate minidump file on the crash? Please post it.

Yeah, there are some workarounds how to achieve it, but I mean that it should be supported natively. Or better, in fact, there is really no need to have some kind of support for Aero Glass - it is satisfactory that all browsers will give up that stupid trend where they disable system native titlebar and render its own titlebar (imitating the same look as system one) on Windows 10 (what's the point to remove something and replace it with something which imitates the removed thing?). It is really mysterious why this wrong behaviour has been implemented for Windows 10 only and it works correctly on any other system. I guess that this trend comes from Win10's UWP applications that do exactly the same (replace default DWM-rendered titlebar with its own GDI rendered parody).

Sometime ago, I reported this issue into Mozilla's bug tracker, but it seems it was completely ignored. Now, on FF 67, on my work computer, Aero Glass in FF still works correctly but on my home computer the CSS property "moz-win-glass" is ignored. Maybe if more users report this issue to Mozilla, some developer will care about it. https://bugzilla.mozilla.org/show_bug.cgi?id=1418759

You have to use older version of Aero Glass to change the blur radius of non-aeroglass blur area. This feature has been temporarily disabled in the last version, because it had a few weird side effects. It may be added back later.

It sometimes takes a while for PayPal to propagate its information to our server, so please be patient if you don't get any e-mail immediately after your donation.