Bug 61934 - Provide Live Update When columns of a table are adjusted using the Table Properties
Summary: Provide Live Update When columns of a table are adjusted using the Table Prop...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) rc
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: Writer-Tables-Enhancements Writer-Table-Properties-Dialog
  Show dependency treegraph
Reported: 2013-03-07 02:45 UTC by narayanaras
Modified: 2018-12-03 19:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Shows how changing column-width is an impossible task (2.34 MB, video/x-msvideo)
2013-03-07 02:45 UTC, narayanaras

Note You need to log in before you can comment on or make changes to this bug.
Description narayanaras 2013-03-07 02:45:38 UTC
Created attachment 76069 [details]
Shows how changing column-width is an impossible task

Problem: Writer provides a "Table properties" dialog, using which we can adjust the column widths and also the entire width of the table.

In a multiple-column table, we can change the width of any/all columns.

However,, the main problem is that the entire process has to be done "blind-folded": We cannot see the effect of the changes we are making. If we change more than one parameters, we are lost.

The only way to proceed is to adjust the parameters one at a a time, click OK to see what it did; and come back to the "Table properties" dialog. Keep repeating till we achieve good results.

This is unnecessarily tedious.

Provide a "live" preview" check box (or make it default behavior). 
Whenever any column-width is changed, it should reflect in the actual document.

If the user presses OK, the changes should be implemented.
If he clicks on CANCEL or presses ESC, the changes should be abandoned.

See attachment for demo.
Comment 1 Joel Madero 2013-03-07 06:36:37 UTC
Confirmed as valid enhancement request.

Marking as:
New (confirmed)
Enhancement (not a bug, behaves as it's intended but your suggestion is quite good :) )
Medium (probably hard to implement but would be useful, leaving at medium)

@Narayanaras - in the future please be a little more straight forward in your bug reports. They should have an enumerated list which says how to do what you're doing, expected/desired and observed. Just makes it easy for QA to read through the bugs. For an example you can submit a bug through bug submission assistant which already has the template set up.

Thanks for the great idea.