bigmuscle

Could you enable verbose logging and provide full debug log then?

Could you describe your display setup? Do some visual glitches appear on the screen? I already saw this problem but I'm not sure what it could cause.

If correctly injected and configured, of couse, it does:

If I have some time, I can create small application which returns the rectangle in atlas belonging to the part which you specify as parameter.

If you didn't use PayPal donate button then send me your donation information in PM... otherwise, you should be able to login using your PayPal e-mail and postal code.

Ok, in any case, I found that the e-mail is not delivered to some addresses and I cannot say why. Maybe the remote server evaluates it as a spam and completely denies its delivery.

What about reading one post above?

I can confirm DWM performance drop in Windows 10 but I am not able to specify if it is Aero Glass-related or not. Sometimes, DWM's memory usage goes up to several hundreds of MB but restarting dwm.exe doesn't reintroduce this. So hard to reproduce. I will not solve this problem before Win10 RTM is released.

I recommend to read this http://www.msfn.org/board/topic/173139-read-first/

Unofortunately no. Only PayPal is possible - but during the donation, it allows you to pay with your credit card.

Of course, it is classic DWM frame so it is rendered as any other window frame - except it ignores window styles WS_MINIMIZEBOX and WS_MAXIMIZEBOX.

Not yet, because it is not working correctly yet. There are also certain limitations: a) extra DLL which needs to be injected via AppInit_DLLs registry key b) no icon/minimize/maximize buttons on titlebar (I don't know how to add them expect completely manually drawing/handling them) c) additional immersive tasks is gone, i.e. no possibility to switch to fullscreen, etc.

What can you notice at this picture

Send me your PayPal address and your old and new keys, possibly whole debug.log file which contains this data - do it over PM.

Just a small experiment I updated 64-bit build which now contains new registry DWORD settings called FrameMargin (under DWM key) which influences the left, right and bottom margin of the frame (the top margin is not influenced!). The value is in pixels, default is zero. Hint: Default Win10 texture for left and right border is 3px wide and all of these pixels are dark. The rightmost pixels for left border (or leftmost pixels are right border) are stretchable when changing border width. If you increase margin with the new setting, the left and right border will be completely dark for this reason. If you want the left and right border to match the rest of the frame, you need to use your custom atlas file with modified textures for these parts. It is not sure if this feature works completely for all frame or it does not cause some problems, thus only 64-bit build is available for testing. Oh, and ignore the frame on "modern" applications - it looks a bit off with increased margins.

Version 1.3.1 is not intended for build 9926 thus it makes no sense. And build for 9926 does not need any symbols.

huh, is there something wrong or why are you downloading the symbols?

Are you saying you may be able to blur the borders? That would be nice, assuming Microsoft doesn't deviate from their path of ridiculousness and ultimately releases Windows 10 borderless. -Noel No, I'm saying that I can provide a way to set theme rects, ints and margins for DWM which you would normally set in .msstyles theme. Yes, you can achieve blur on borders with it, but I cannot provide correct values to set. You would need to create custom atlas and then experiment with the values.

According to window borders, I can add hooks to allow custom settings of frame margins and sizes. However, I cannot ensure that it will really work because I am not able to find correct numbers to display it correctly.

If debug.log grows up, don't you mind that it would be good to provide its content?

For Win10 installation, you should follow the guide, point 2: http://glass8.eu/guide.html If you are unsure about the installation steps then you should not install it at all, because this is only development version intended for testing and not for consumers.

I updated the links with version which fixes glass safety zone resizing on multiple displays.

The link is in your e-mail. If you can't find it, read this topic first http://www.msfn.org/board/topic/173139-read-first/

You can use small utility called WinID or Microsoft Spy++ to discover any window's properties.

This popup should not appear there at all unless your donation key is wrong. Check debug.log for more information.