Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualTom KQT

Posted 30 October 2013 - 04:57 AM

Actually everything is working correctly. You called SetWindowPos and it did its job without errors. When the function tries to change position or size of a window, it's said that it will send the WM_WINDOWPOSCHANGING message. And the default handler of that message checks the size and fixes it if it's out of limits (it uses the WM_GETMINMAXINFO message). That actually is what that message was made for - to give you (or the system) a way how to easily check the validity of newly set window size - and to do whatever you need as a reaction to it.

But nobody prevents you from handling WM_WINDOWPOSCHANGING yourself. And you even can use a flag when calling SetWindowPos to disable sending WM_WINDOWPOSCHANGING.

 

You want something what's not allowed by default. But you still have ways how to do it. So I don't understand why are you complaining ;)


#2Tom KQT

Posted 30 October 2013 - 04:56 AM

Actually everything is working correctly. You called SetWindowPos and it did its job without errors. When the function tries to change position or size of a window, it's said that it will send the WM_WINDOWPOSCHANGING message. And the default handler of that message checks the size and fixes it if it's out of limits (it uses the WM_GETMINMAXINFO message).

But nobody prevents you from handling WM_WINDOWPOSCHANGING yourself. And you even can use a flag when calling SetWindowPos to disable sending WM_WINDOWPOSCHANGING.

 

You want something what's not allowed by default. But you still have ways how to do it. So I don't understand why are you complaining ;)


#1Tom KQT

Posted 30 October 2013 - 04:54 AM

Actually everything is working correctly. You called SetWindowPos and it did its job without errors. When the function tries to change position or size of a window, it's said that it will send the WM_WINDOWPOSCHANGING message. And the default handler or that message checks the size and fixes it if it's out of limits (it uses the WM_GETMINMAXINFO message).

But nobody prevents you from handling WM_WINDOWPOSCHANGING yourself. And you even can use a flag when calling SetWindowPos to disable sending WM_WINDOWPOSCHANGING.

 

You want something what's not allowed by default. But you still have ways how to do it. So I don't understand why are you complaining ;)


PARTNERS