|
|
Screenshot with minimum PP width enabling access to XYscale ratio controls. See empty space in inputs. image pane - minimum width with XYratio controls.png (7,928 bytes) |
|
|
We do not control directly widget size, this is Qt which does most of the work. The input spinboxes have already their size policy set to QSizePolicy::Minimum: which means: "The sizeHint() is minimal, and sufficient. The widget can be expanded, but there is no advantage to it being larger (e.g. the horizontal direction of a push button). It cannot be smaller than the size provided by sizeHint()." So if those widgets are displayed with a large width on your computer, this is not because they are large by themselves, but because something else allows them to grow in size and I suspect the color profile combo to be the real issue. Note also that the widget size has to accommodate the width needed for the minimum and maximum values a user can enter. And for aesthetic reasons, it is not possible to size the widgets using only their content because in such case each widget will have a different size, will not align nicely, hence making the dialog ugly. |
|
|
hi jean, you're probably technically right... but scribus has indeed the bad habit of forcing a too wide properties palette... or even just automatically resize the palette to unpractical widths. it would be nice if somebody could collect which fields are producing this and how to limit the growth without making the fields useless. |
|
|
Thanks jghali for providing this extensive answer. I dont think you adressed one of my proposition in your answer : The worst issue with this uselessly-wide inputs is when having to reach the "keep XY scale ratio" controls which are on the far right of the inputs. Because then, i have to adjust the PP width to make it much wider. For all other uses, PP can be small width and only left part of inputs are displayed but this doesnt prevent to use them. That's why I proposed a practical solution: to have the "Keep XY scale ratio" controls LEFT of the scale values input. With such a position, the uselessly-wide inputs wouldnt a problem anymore (except "esthaeticaly", which is not so bad as "practicaly"). Is this a possible controls layout ? |
|
|
>> That's why I proposed a practical solution: to have the "Keep XY scale ratio" controls LEFT of the scale values input. Except that won't work. You should have noticed that the width of the string shown in that control is much shorter than the width of the scale input fields. So this is not that control which lets the scale input fields grow in size. As already mentioned in my previous response, the widget which has the biggest needs for size is the color profile combo box. I can reduce a bit the need for size of that widget if we accept that some of the profile descriptions will be elided when user reduce the property palette width. |
|
|
jghali I dont understand your answer . It could be you didnt understand my post neither so i upload a sketch of the proposed change "scribus move ration controls.png" scribus move ratio controls.png (8,338 bytes) |
|
|
There was indeed some misunderstanding. However I don't like that solution: 1) it is a workaround and does not fix the real problem 2) it is ugly I've committed a patch (r22932) which reduce the image tab need for width when color management is enabled. Please test. |
|
|
I dont know what has changed. I can't say it improves. The "chain" button (for "keep or dont keep ratio" feature) is still far right and disappears first when trying to make palette less wide. Could it be it's related with the lenghty ICC named "Compatible with Adobe RGB (1998)" and other such lenghty ICC names ? |
|
|
Same access issue happens with other buttons that are far right in the palette. For example the shape change button. (related : 0015850) |
|
|
jghali : it's strange that you find it's ugly to have chain buttons on the left of inputs rather than on the right. Maybe it is a matter of habit, but not of absolute beauty if such exists. And even when these were not as nice, i like it better to be able to see existing buttons so i can access them. |
- Anonymous
