Description: When I try to change one column width it changes the one to the right. I do that for 12 columns (major hassle) and if i enter less than the remaining space in the last column it adds the balance to the first column. This is maddening. Steps to Reproduce: 1.change width of left column Actual Results: each column to the right changes in turn Expected Results: the table width should be shortened/lengthened based on sum of the columns as i enter them. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Please put a switch in the column width or table tab of table properties to tell the software to automatically adjust the table width vs. constantly changing columns to force the assumed table width. I have screenshots if you want them.
Fully agree.. again not sure if this being whole idea.. and another option being needed or this simply being wrong
It depends on the Alignment (first tab in the dialog). If you do not use Automatic but Left, for example, the column width is set as expected. See also https://help.libreoffice.org/7.2/en-US/text/swriter/01/05090100.html Admittedly, the UI makes it not easy to understand.
*** Bug 139096 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #2) > It depends on the Alignment (first tab in the dialog). If you do not use > Automatic but Left, for example, the column width is set as expected. See > also https://help.libreoffice.org/7.2/en-US/text/swriter/01/05090100.html > > Admittedly, the UI makes it not easy to understand. This bug the cause for me to created bug 139096 bug 139098 bug 139370. Switching to left as such doesn't fix it. You need to check adapt width also. This is not end-user friendly. I call it even bad User Experience (UX). So UX department should 'care' about this bit more. Tables are commonly used. What the user wants isn't really uncommon. To way to archive that is uncommon, and complex. Which probably not necessary, IMHO So it make sense to improve this. I did few suggestion attempts(see closes see also). Happy to go another direction.. but I think something should be done here to make this better (obviously without breaking this for other use-cases) So I still like a second opinion (Stuart). And I would even like a third (Baron or Justin). Currently it's 2 against 1, IMHO. [Yes, there are cases where you're vote counts for 2.. but would like to make an exception here. I see this as too important]. I shut my mouth with clear 2:3 vote..
(In reply to Telesto from comment #4) > This is not end-user friendly. I call it even bad User Experience (UX). So > UX department should 'care' about this bit more. The ticket was about "doesn't work". We likely do have another requuest for a better UI, that's why my take is still NAB/WF (or duplicate).
(In reply to Heiko Tietze from comment #5) > (In reply to Telesto from comment #4) > > This is not end-user friendly. I call it even bad User Experience (UX). So > > UX department should 'care' about this bit more. > > The ticket was about "doesn't work". We likely do have another requuest for > a better UI, that's why my take is still NAB/WF (or duplicate). No objection . but please give some kind of summary suggestion (or create a bug yourself) which is UX proof. I created 3 additional bugs (see duplicate + duplicates there).. Which all being closed. It feels like a kind of filling bureaucratic forms which requires a certain format to be processed, but people given a blank paper (not a form) with always end up with a stamp "denied" or "not admissible" because not matching criteria And a certain point I'm out of idea's of 'solutions' and stuck with only a problem description without clear alternative solution. Whereas problem descriptions without solution direction is seen as to unspecific/undirected and closed because that.
(In reply to Telesto from comment #6) > ...please give some kind of summary suggestion... Would dig the bug tracker myself with pleasure but got flooded with tickets. So please check yourself on what _existing_ ticket the discussion about UI/UX improvements for this dialog fits best.
(In reply to Heiko Tietze from comment #7) > (In reply to Telesto from comment #6) > > ...please give some kind of summary suggestion... > > Would dig the bug tracker myself with pleasure but got flooded with tickets. No clue how that could happen
Hmm, digged out one of my own bugs: bug 114633
*** This bug has been marked as a duplicate of bug 114633 ***