o-smirnov
commented
8 years ago This is your code, right? It could be that the default size policies of the Qwt plot widgets have changed.
The way the widget layout managers work, they interrogate the widgets about what their minimal size is, and allocate space accordingly. If the widget says "I can't be squeezed to less than Y pixels in height", then it gets Y pixels no matter what. This is determined by size policy settings: http://doc.qt.io/qt-4.8/qsizepolicy.html#Policy-enum
The "freq/l/m" controls here have a fixed height, and they do take up a lot of real estate. You could look into making them more compact somehow (single line? Smaller fonts? Minimal margins?)
As for the remaining space, you could try to change the "minimal size" of the plot widgets, and play with size policies to allow them to be resized to that minimal size. At the moment it looks like the plot widgets want to stay big.
twillis449
OK- so I'm testing Meqtrees on both ubuntu 14.04 and 16.04 to test numpy behaviour. I managed to get a simple script where I pop up four image windows showing test beams to work. This lap top has an intrinsic display of 1600 x 900 pixels. The bottom two windows are only half displayed.
I think this is a high-level windows management problem. At one time way back when one could get something like 6 to 8 initial displays in the browser, but the number seems to be shrinking over time. When I 'float' the window the complete contents do appear (including the control GUIs).