New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: Rewrite WM_NCHITTEST & WM_NCCALCSIZE handling. #139
Conversation
windows: portability: Support Win7 and early Win10.
- Use 0 MARGINS in DwmExtendFrameIntoClientArea - Now resize hitbox lies outside the window frame. - No window border is visible on Windows 10 or 11. - Reference: melak47/BorderlessWindow#13
Hey @bitsdojo, I know open source hasn't been much rewarding for all the hard-work. Unfortunately, I'm just a student so can't sponsor your work. Anyway, feel free to have a look/merge when you get time. Best, |
Appreciate your message. I've been offline in the past month and a half due to a medical issue but I will have access to my computer next week and I will take a look over the issues. Bit |
Thanks for the report. I will have a look & will require your feedback again. |
@ashutosh1211 I can't seem to find any unsafe calls. Make sure you have the |
@alexmercerind the window border seems to wider now, is this intended? |
On Windows 7 & 8.x it is. And there's no workaround if you want the "re-size area" to stay outside the window frame. See Google Chrome on Windows 7 or 8.x, it will also have this border. |
DwmExtendFrameIntoClientArea
.WM_CAPTION
from the parentHWND
.Windows 11
Windows 10
Other changes: