bigmuscle

ModernFrame.dll has been updated. Link is on my website. Now, it hooks all processes which may open app frame, so don't worry about one console for any needed process. Known issues: - inactive frame has wrong colour for caption title

why don't you release the current "experimental" build? According to my experience (and I believe, by the other testers here experience) this build is stable enough and working fine on the released Windows 10. I know you are "perfectionist" but it's simple not possible to release 100% bug- or issue-free builds. Because it simply is not stable and I have already fixed many bugs since last build Remember that this is very low-level application so if it is stable for you, it does not mean that it is stable globally. E.g. patching incorrect memory bytes can have no visible impact for you, but may totally mess the system for someone other. And complains about debug window are much more acceptable than complains that this application killed your system completely.

Could you try to modify registry directly? In HKLM... maybe just GUI app does not save this settings correctly. If it does not work, could you try my utility what status it reports on Win10: http://glass8.eu/out/BatteryLogger.7z

no, it should be still same... what's the problem: glass does not disable on battery or glass doesn't enable when not on battery?

Sorry but I didn't. There wasn't any checkbox or agreement I had to confirm, just a plain download.If I would have to do, I would do it and if that also would mean to send error logs to you I would too but since there's nothing like that, I can use and customize it (no illegal stuff) for my personal use like I want. Thats my opinion. Your opinion is correct here. Debug versions for Win8 contained message box "You are using experimental build etc. etc." that user had to confirm. Users were convincing me that they know it is debug build so they don't need to be bothered with this information. Thus I didn't add it in debug build for Win10. But yes, you are right, I will return it back and users will have to confirm it explicitely.

Sorry, but this is not about legit key, it is not either whether debug info is necessary for you. Remove it, modify it as you want, it is your computer. But you downloaded debug version, you agreed to help with development by downloading this version so spamming this forum with guides "How to remove debug means and make full version from beta" is a bit rude, does not help with development at all and only make this forum full of useless stuff.

Stop discussing things unrelated to Aero Glass. If someone wants to bypass some limitation in my software then he should not use testing development version.

I got it, the same thing happens on Win8 when main monitor is at center.

This is interesting idea which I could check

You either used wrong Aero Glass version or applied some 3rd party tweaker which changed your settings to fully opaque.

Sure, just use my GUI utility which allows you to specify different values for both active and inactive frames. Just the opacity level cannot be different on Win10.

Because it is different file. Compiler/optimizer can just inline some functions, change call conventions etc. so the technique "replace this function with my own implementation" cannot be easily used.

Ah, I could fake multiple monitors in Win8.x just by setting the number in virtual machine settings. This does not work in Win10. According to your debug.log, it seems that only first 2560px is detected and thus smaller glass safety zones used. It results in glitches on anything beyond 2560px. Also, I'm afraid that making FrameMargin won't be possible. It is much more difficult to implement on 32-bit so I thought I could add it as x64-only feature, but it seems that setting any margin completely breaks AeroSnap feature.

It will be glass safety zone problem. Any special steps to simulate multiple monitors in VMWare? In Win8, I just selected "3 monitors" in machine settings and then selected "Connect on VGA" in control panel. The same procedure results in "Cannot save display settings" error on Win10.

It depends on the problems/bugs/feature requests which appear in next 1-2 weeks. Since I don't use W10 myself, I cannot test it much. There are still some bugs which I need to address but also some things which I am not able to implement correctly on Windows 10 RTM (FrameMargin, different opacity for inactive frames etc.). There is definitely an issue with triple monitor setups. Everything is just fine on screens 1 and 2, but everything displays artifacts on screen 3 in glass enabled areas when hovering over caption buttons etc... ​ If you need any debug info from me to diagnose the issue let me know. Yeah, provide your debug.log. But I see it as difficult to catch because it seems that multiple monitors virtualization does not work in Win10 with VMWare. In Win8, I can simulate any number of monitors but it displays error message "Cannot save displays settings" in Win10.

It depends on the problems/bugs/feature requests which appear in next 1-2 weeks. Since I don't use W10 myself, I cannot test it much. There are still some bugs which I need to address but also some things which I am not able to implement correctly on Windows 10 RTM (FrameMargin, different opacity for inactive frames etc.).

ModernFrame replacement for 10.0.10240 Known issues: * you need to use old AppInit_DLLs method to inject * ApplicationFrame.pdb symbols are needed - use dbghelp.dll and symsrv.dll from Aero Glass installation * frame theme change is not fully optimized * frame title is drawn by ApplicationFrame so its look does not fully fit in frame * some icons may be missing, e.g. "Go back" frame icon * I don't alter frame height (ApplicationFrame uses 32px) * only 64-bit version now !!! THIS IS EXPERIMENTAL DEBUG BUILD ONLY !!! Link on my website

Hello, It has been said several times that Windows 10 version is for debugging/testing purposes only and for ADVANCED users only. All instructions to use any version of Aero Glass is described on my website and if someone is not able to read it and follow it, then he is not advanced users and he should not use any testing versions of any software. Due to the nature of Aero Glass utility, it can be more harmful than anyone thinks. Also, all needed information has already been said during the development of Aero Glass for Win8.x - if someone wasn't participated in the development of previous versions, he is not advanced user. If non-advanced user use it, I will not provide any support for him. I'm locking this topic, because it makes no sense. But once more in capital: !!! AERO GLASS FOR WIN10 IS ONLY DEBUGGING BUILD INTENDED FOR ADVANCED USERS !!!

Then enjoy random crashes when some debug output will be written to invalid memory address instead of the console.

Use reverse procedure that you used for installing.

Not now, maybe later. It is not a priority, because frame size can be influenced by altas+layout which I will describe on final release. Something in your system sends a message that system colors have been changed and thus Aero Glass reloads the settings.

http://glass8.eu/guide.html

I didn't know that I distributed ModernFrame.dll with AeroGlass for build 10240. So probably my mistake...

No, it is because users screw it up by using some unsupported installer on Windows 10.