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

Inconsistent glfwMaximizeWindow behaviour for undecorated windows #899

dougbinks opened this Issue Nov 19, 2016 · 0 comments


None yet
2 participants

dougbinks commented Nov 19, 2016

See forum thread glfwMaximizeWindow bug on Windows 8.1 and Windows 10 with undecorated window.

On Windows an undecorated maximized window will cover the entire monitor area, and not just the working area - so hiding the OS task/menu bar. Decorated windows only maximize to the working area, as do both decorated and undecorated windows on Linux Mint. I'm not sure of the behaviour on Mac OSX.

Whilst this follows the OS functionality since it uses ShowWindow(window->win32.handle, SW_MAXIMIZE), it makes it difficult to create an undecorated window which behaves like a decorated one.

I can think of a few solutions for this:

  1. Modify glfwMaximizeWindow
  2. Add a hint or compile flag to control behaviour of glfwMaximizeWindow
  3. Add functionality to enable developers to maximize a window to the working area, either through a Get of the monitor working area or an alternative maximize function.

If needed I can do some of the work, but I don't have all the OSs GLFW supports if the solution alters behaviour for other systems.

@elmindreda elmindreda added the Windows label Nov 21, 2016

@elmindreda elmindreda self-assigned this Jan 4, 2017

@elmindreda elmindreda removed this from High Priority in Review Queue Feb 7, 2017

@elmindreda elmindreda added this to the 3.4 milestone Mar 27, 2017

@elmindreda elmindreda removed their assignment May 2, 2017

@elmindreda elmindreda self-assigned this Oct 31, 2017

@elmindreda elmindreda modified the milestones: 3.4, 3.3 Oct 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment