bigmuscle

Additional notes: * up-to-date version of ModernFrame.dll is part of installer, separate DLL will be published later * current version of UxThemeSignatureBypass is NOT fully compatible with this version of Aero Glass (missing atlas layout support, misaligned glow effect on some windows etc.)

Aero Glass for Win8.1+ v1.4 * Windows 10 10.0.10240 support* hardcoded symbol patterns for current version of DWM in Win8.1* added build numbering* hopefully fixed crash on device resource change* blur deviation setting partially influences Win10 blur accent too* lots of stability and performance fixes and code refactoring* added >>experimental<< module to enable glass frame on Win10 Modern apps - this requires secure boot to be off* added support for custom atlas layout, format: - each line has format "x;y;z=a,b,c,d" - x, y, z specify the part, its state and the property respectively - a, b, c, d specify position rectangle in atlas image (for z = 8002) or the part sizing/content margins (for z = 3601/3602) - see example layout file for description of individual part identifiers - see MSDN documentation of GetThemeRect and GetThemeMargins function for further information - line "CaptionHeight=n" allows you to change the size of caption buttons to "n" pixels - everything after # is considered to be the comment and is ignored * KNOWN WIN10 LIMITATION: - due to the way how Win10 composes windows frames, it is not possible to fully apply corner radius - for the same reason you can see blurred separation of window caption - it is not possible change inactive frame opacity separately

I know about this. The layout file has been generated quickly by DWM without additional change.

Unfortunately, I do not use this software and I don't know the technique which it uses. If it uses standard layered windows to get the full transparency then it is not possible to do anything about this. Such bug randomly appears even with native Aero Glass in Win7. If it uses another technique then I don't know, as I said, I don't use it. Does this happen without Aero Glass? This kind of frame appears when DWM rendering is disabled on the window so if some application disables it for itself then I cannot influence it. What version of Firefox is it?

So should we release today or is there some important blocker which limits you? B)

And? There is no reason to support this build.

Build #160 - probably one of the last development debug builds has been published on my website.

chris2: I tried that and it is not possible - ModernFrame.dll needs to be injected before any application frame is created else it won't be possible to draw on it.

We are approaching build #150 soon... New experimental debug build #149 can be downloaded on my website. Now, 64-bit only. What's new? Mainly stability fixes but I added two experimental features you can play with: - you can change caption buttons size by putting line "CaptionHeight=XXX" into your atlas layout file (it influences both width and height, separate change is not possible!) - you can force DWM to accept system metrics on windows frames in SOFTWARE\Microsoft\Windows\DWM by setting value ForceSystemMetrics to 0x1 (DWORD) - by setting ForceSystemMetrics values to > 1, you can modify frame margins

http://glass8.eu/guide.html

If you move mouse to the top edge of your display, it will roll down the titlebar and it allows you go back just by pressing Restore button. But there seems to be some bug in Win10 that this titlebar does not show sometimes

-Tex-: no, this is not possible doctorwizz: use CTRL+ click on maximize button to switch to fullscreen

AppInit_DLLs registry value: * security risk (aerohost verifies if DLL is correct) * secure boot must be turned off * loads DLL into any process -> DLL can negatively influence behaviour of any application on your system * loads DLL very early in main thread -> race condition can cause any application to deadlock (e.g. black screen on startup etc.) * does not have access to user session -> per-user settings won't be loaded

Yes, this is ok. UxThemeSignatureBypass.dll is not fully compatible with current version of aeroglass/modernframe yet. EDIT: It means, it ignores atlas layout file.

I would like to know If this is normal At this stage of development or if I forget something ? I must admit that I don't understand this. Why non-advanced users bother with non-finished development version if they are not even able to read instructions, guide, notes etc. before downloading? What is the sense in using installer on Win10 if it is marked as "IMPORTANT: Do NOT use on Windows 10 RTM 10.0.10240." ???? And it is not only this... why some users are injecting DWMGlass.dll via old AppInit_DLLs on Win10 when nobody says it to do it so? Why? .... I'm asking because every while I get some bug reports where the only cause it that user was not able to install it correctly. So again for everyone: !!! IF YOU ARE NOT ADVANCED USERS AND YOU ARE NOT ABLE TO INSTALL THE DEBUG VERSION PROPERLY THEN DO NOT USE IT !!!

Yep, long/spaced paths in AppInit_DLLs not supported

My1: you are right, GUI has invalid default value for battery setting

You cannot remove borders at this time, it is just the property of used theme (=atlas).

Does debug window display some "Message 0x..." when you unplug it?

So another development build is coming... It contains multi-monitor and stability fixes. Win8 CP atlas file replaced with Win8 RP atlas file. Added build numbering so you can check which build you are now using. We are hopefully very close to final release now. Just a few small things are remaining. Link for download is on my website. Build is intended for debugging and testing purposes only. Do NOT use on production environment of if you don't accept software conditions.

Spam deleted. Why? Because this discussion makes no sense. Every while, there is some new member registered in this forum which just came in to complain that he wants to use my software without respecting the conditions and only complains and complains and spams this forum still around. Any further posts not-relalated to Win10 development will be deleted from here. If you don't accept the conditions of my software then stop using it. Thank you.

Yeah, I noticed it too but I don't know what the cause is

This thing is still under development so it makes no sense to explain it now currently, it is just rectangles and margins extracted from theme.

Hello, about donation: please could you activate verbose logging (via registry editing in HKLM - see guide on website) and then provide debug.log file? about glitched window frame: use atlas file only with compatible windows theme

No, it is not. Back arrow is just a button drawn by ApplicationFrame.dll. It seems to be black for active windows and grey for inactive windows. But it may depend on app, because some apps draw the titlebar with white color.