Application window can only shrink, not grow, after switch from Qt 4 to Qt 5
-
wrote on 6 Feb 2019, 16:27 last edited by
Recently, we switched from Qt 4.8.7 to Qt 5.12.0. One of our applications has a small window of about 600 by 400 pixels when it starts up. After it has started, users could resize it, meaning that they were able to resize the window to a smaller size, but also to a larger size. However, after the upgrade from Qt 4 to Qt 5, the window can only be made smaller, not larger. This is rather annoying, as a user who has downsized the window, can never make it larger again :-(
I have searched through our code trying to find the root cause for this, but up until now have not found anything. What exactly could be causing this behavior? Any hints on specific things (classes, function names,...) I should look for?
-
Nothing that could cause this comes to my mind, but I have one recommendation: try upgrading to Qt 5.12.1, it came out just recently. In my experience, the .0 release was super buggy, the .1 fixed a lot. Perhaps your issue was fixed as well (if it is a bug).
On my end (working both on QtWidgets and QtQuick apps), I have not seen such resizing issues - everything works correctly.
-
Hi
So if user resize the default 600x400 to smaller, they cant even make it
the start size again? -
Hi
So if user resize the default 600x400 to smaller, they cant even make it
the start size again?wrote on 7 Feb 2019, 13:23 last edited by@mrjj said in Application window can only shrink, not grow, after switch from Qt 4 to Qt 5:
So if user resize the default 600x400 to smaller, they cant even make it
the start size again?That is correct.
-
Hi,
Can you show how you setup your widget ?
-
wrote on 8 Feb 2019, 08:08 last edited by
@SGaist said in Application window can only shrink, not grow, after switch from Qt 4 to Qt 5:
Can you show how you setup your widget ?
I wish I could... but it's proprietary legacy code and it's hard to understand and trim down to the essentials...
But no worries: in the mean while the problem is solved. I upgraded from Qt 5.12.0 to Qt 5.12.1 and the problem magically disappeared! :-)
-
Yet another proof that 5.12.0 was a big mistake :-)
OK good that things work for you now. Happy coding!
1/7