On Sep 16, 2013, at 12:55 PM, Alexandre Julliard wrote: > Ken Thomases <k...@codeweavers.com> writes: > >> --- >> dlls/user32/driver.c | 12 ++++++++++++ >> dlls/user32/user_private.h | 1 + >> dlls/user32/winpos.c | 2 ++ >> 3 files changed, 15 insertions(+), 0 deletions(-) > > It's better to avoid adding entry points that don't correspond to > Windows APIs. Instead you should request the info when you need it.
Cocoa makes use of the size limits "spontaneously", not just at the time when the user begins to resize a window. On OS X 10.7 and later, the user can resize windows by their edges and the cursor changes to show the available operations. So the limits need to be set in advance and updated whenever the app would respond differently to WM_GETMINMAXINFO. Since I have no way of knowing in advance when it might do so, I figured I would either have to poll (more or less) or piggyback on user32's queries. Also, it's not clear to me that apps will tolerate WM_GETMINMAXINFO occurring at times when Windows would not send it. I'll rework the patches and I guess we'll find out. -Ken
