Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I was wondering why the mouse pointer seems to change to the "resize" one inconsistently - the left, bottom and right changes to the resize pointer as you touch the edge and continues to be that for a few pixels outside, whereas the top becomes resize pointer a few pixels below the border and changes back almost immediately after.
The non-client window region has rounded edges (as you can see in the picture) like they did in Windows 7. It seems that the edges of the window are clipped so they effectively have an invisible frame. But they didn't clip the top of the window as much. -
I have a similiar effect on some windows of Visual Studio 2010 on Windows 7. E.g. the search window, if I go over those buttons, the old style buttons appear, slightly shifted. It's really annoying, as it immediately attracts my attention every time.
But Microsoft has to implement such bullshit like the delayed reaction to the input in MS Office, there is no time to fix errors.
While messing around with the Windows WM_NCPAINT message, I forced the WindowProc to return without calling DefWindowProc.
This resulted in interesting effects when pressing mouse buttons down on the right hand side of the title bar. This is on Windows 10.
Bottom part of the image is when I clicked on things and is Windows 9x-XP style. Top part of the image is when the window was deactivated and is Vista/Windows 7 style. Once they appear, the buttons behave as they did (visually - e.g. highlighting) as they did on those versions of Windows.
Just found it funny to see older bits of the Windows UI still hanging around behind the scenes!
random
legacy
wm_ncpaint
windows