bigmuscle

NoelC: I checked your log and it contains "Message 0x219, wparam = 7, lparam = 0" where 0x219 means WM_DEVICECHANGE and wparam 7 means "A device has been added to or removed from the system.". Would it be possible to confirm that DWM does not restart when Aero Glass is not used?

NoelC: error number 0x8898008DL means MILERR_NO_HARDWARE_DEVICE which states "No HW rendering device is available for this operation." so we must search for the reason why this happens - does something in your PC turns your graphic card off? Or something which could generate such error. Unfortunately, it's impossible to track where this error occured. Reinholder: there seems to be one big thing which you probably don't understand. Software available at http://glass8.berlios.de and all instructions written there are for Windows 8. That's why the website states "Aero Glass for Windows 8". And for this system, the instructions are completely valid. Software for Windows 8.1 has NEVER been released at all!!! Then it is really clever step to install unfinished beta testing version of any software... People don't realize that this piece of software is very low-level thing which patches memory bytes and which can be very harmful if implemented improperly. It's very easy to say "We know it's beta", but when it accidentally patches wrong memory bytes, will it really be easy to say "I know it was beta and that's why all my data has been lost. It was my fault." ??? Also command window is not there to annoy anyone. It's there for the purpose of testing/debugging and I use it a lot. The sense of all released testing versions is not to give you fully usable tool but to give you a preview of what I'm currently working on. If you don't like it, do not use it.

Hancoque: there will be a setting for it PandaX: it's Windows limitation, because space character serves as separator there NoelC: if DWM restarted due to some internal error, it should be trackable in system log (eventvwr > Application log)

As I already said, it wouldn't influence inactive windows at all, because

MrGRiM: then it's not hard to read this value. But 50% may be a problem in Win8.1 theme so I will see how it looks like. ColorizationOpacity is already respected if you do not set custom color/blur-balances for inactive colorizations.

OK thanks for clearing that up, one thing though, there are settings in the theme for the opacity of the glow image, this opacity can be set for active and inactive windows, I think this is why I thought the glow looked perfect at first, because I think that it's only being set at 100% and ignoring the theme value, it should be set at 80% for active and 60% for inactive windows if it was reading my theme settings. So is there a way we could have the opacity correctly applied from the theme settings or have you done it this way because the default windows 8 theme has those values set much lower? I can see the default aero theme values have been set to 50% opacity for active and 20% opacity for inactive, if that's the problem and why you are using a preset value of 100% then maybe you could make this configurable with a registry setting or otherwise let it read the correct theme opacity values. Actually, I don't know whether OPACITY settings in theme is really intended for glow effect, because I don't see any connection to it there. But on the other side, it's not really usable here, because when glow is currently rendered, only caption text is known and there is no connection to the window (so it's unknown whether it is active or inactive window).

MrGRiM: glow effect at windows which are already opened during DWM startup is wrong. Although it may look correct to you, it just uses some random value. The glow effect on Explorer (and Ribbon) windows is rendered by UXTheme (and not by DWM) and it's setting is influenced by your theme. The glow effect which you described as "After restore" is the only one which is correctly rendered by DWM and it looks how your theme atlas looks.

This error means "Invalid Signature", in other words "License file does not match machine id". It's the intention.

AERO GLASS for Win8.1 Candidate for Release Candidate I'm not sure if this build satisfies you. I didn't have much time so it does not contains much changes but maybe contains new bugs :-D * simplified some things about settings/theme loading * registry settings to enable/disable glass when running on battery should work again (default is "Disable glass on battery") - probably disables blur effect only and leaves full transparency now * multiple monitors fixes * offscreen render target fixes (e.g. Magnifier) * prepared some parts of code to build 32-bit version soon * caption glow is now stretched to whole frame height * fixed crashes/weird rendering when resource domain changes (e.g. when exiting games, changing video adapter etc.) * maybe some other fixes which I don't remember

1) it has been written million-times here 2) any experienced betatester should know it, if you don't know it then you should not be using experimental beta version of this software 3) if the answer does not satisfy you then look at point 1)

The fix for magnifier for just one "if(bUseOcclusion)" :-) "Failed to load reflection file (0)" is actually not an error, because (0) means "no error", it simply means that file has not been specified and there is nothing to load.

Right, I forgot that offscreen render targets (such magnifier) do not use occlusion optimization and thus my code can crash.

1. Aero Glass for Win8.x does not modify any system files. 2. License is shared between both versions. At least, it should be. But because Win8.1 version is still in development I cannot ensure it now. But at the end, you will not need new license for Win8.1.

Maybe it's the same problem that Hancoque described in post #561. I will try to reproduce it.

NoelC: my library should not do it. But I cannot say that e.g. some internal DWM/console mechanism cannot do it - it is beyond my knowledge. Hancoque: without Aero Glass, you would not be able to use modified theme at all (unless you use some other method for theme signature bypassing - in such case, the situation is same)

You have probably enabled theme signature bypassing and if you use custom theme then yes, it can cause black screen and there is nothing to do about this.

If DWM crashes, there should be minidump.dmp file created in Aero Glass folder which allows me analyze the cause of the crash.

yes, I found a bug in code.

http://glass8.berlios.de/win81.html

yeah, I'm still saying that I will add timestamps but always forget to do it. Nevermind, I found it in the log and now I have to find a reason why DWM loads theme earlier than it is notified that user has logged in (so my Aero Glass cannot access your HKCU during theme loading). It should normally not happen.

So when this happens again, just provide debug.log. Maybe I forgot about something. I just only noticed that glow effect is not correctly updated on existing windows on reboot, but it's minor issue.

So if this is "one of" the possible ways to install Aero Glass, then what are other possible ways? Thanks for any info on this. --JorgeA As the guide states "It depends completely on you how you install the library into your system.". You can for example write your own dwm.exe wrapper, replace system files etc. AppInit_DLLs way is used for the reason that it's probably the only one non-violent method.

Symbols can be downloaded from MS servers. We cannot host them here.

No! I don't need screenshot which is similar. I need screenshot which EXACTLY correspond to debug.log so I can check all coordinates, compare them and see what is computed wrong. EDIT: so, I fixed the problem. If I disable video driver in VMWare, it allows me to rotate display and find the problem :-) The problem was that rotation does not only change screen degree to 90°/270°, but it also change from top-bottom orientation to bottom-top and rendering rectangle where bottom < top simply didn't work.

NoelC: it's not the final, it must be tweaked but: it's different from Win8.0 version (that's why I mentioned margins problem), but it is still same as it was in Beta 3 (if you have different result it's because you have different image in atlas.png than it was in glow.bmp - and yes, I checked, your glow.bmp, which you sent here, is different from your atlas). The most correct way (and most similar to Win8.0) was in Beta2, but it caused misalignment of caption on maximized windows due to the possible bug/limitation in DWM.