On Mon, 9 Nov 2020 09:31:44 -0800 (PST) Hamish McIntyre-Bhatty wrote:
HMB> Originally posted at
HMB>
https://forums.wxwidgets.org/viewtopic.php?f=23&t=47598 but I have since
HMB> been advised that I should post here and might get the attention of the
HMB> main GTK developer (Paul?).
HMB>
HMB>
HMB> As I first reported here:
https://discuss.wxpython.org/t/setminsi ...
HMB> nces/34914
HMB> <
https://discuss.wxpython.org/t/setminsize-and-setsizehints-platform-differences/34914>,
HMB> I have noticed differences in the way SetMinSize() and SetSizeHints() work
HMB> depending on whether the X11 or Wayland backend is used.
Unfortunately I know very little about Wayland yet because I just can't
find time to really sit down and read/experiment with it, so I can't help
with this and couldn't reply anything really constructive to your message.
However I can say that it would be very useful for _us_ to have a simple
test case, in C++, showing the problem. If you could please create one as
described in
https://trac.wxwidgets.org/wiki/HowToSubmitPatches and open a
ticket with it, it would be helpful.
HMB> It seems that SetMinSize() and SetSizeHints() are ignoring the window
HMB> decoration in the minimum size calculation on X11,
But wait, rereading this more carefully, I actually think it might not be
a Wayland problem at all because what you write is not the expected
behaviour under X11. Only SetClientSize() should ignore the window
decorations, SetMinSize() should take them into account. Unless we attach
different meanings to the word "ignore" so, just to be perfectly clear:
calling SetMinSize(100, 100) should prevent the window from being reduced
below 100 pixels in total size, which means that its client size will
become strictly less than 100 in both directions when it has its minimum
size. If this is not what you see with X11, please report the WM you use.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/