[Libreoffice-ux-advise] [Bug 90883] WRITER: Selecting rows/columns doesnt change the behaviour of insert buttons

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sun Apr 26 10:01:15 PDT 2015


V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
                 CC|                            |vstuart.foote at utsa.edu

--- Comment #1 from V Stuart Foote <vstuart.foote at utsa.edu> ---
@Jay, hate to state the obvious, but Calc's cells/columns/rows have no data
structure in common with Table's cells/columns/rows.

Yes it is worth looking at for consistency of UI. I'm not sure of all details
of the exposed attributes for Writer Tables, but the enhancement may simply not
be possible.

In general, there is no reason to expect .uno commands affecting Calc sheets to
function the same when the .uno command is affecting Tables in Writer (or other
modules that implement tables).

For Writer Tables the insertRow, insertColumn UNO commands insert  rows and
columns one at a time, it does not replicate the multiple row, or multiple
column selected "counts" as implemented for the actions in Calc. 

Likewise, selection of rows/columns in Calc is not the same as its counterpart
in Writer Tables.  These selections also happens to use the same UNO
commands--but also have different actions appropriate to the Object type.

For example, notice that with a Table, you can select multiple rows/columns
with <Shift> selects, but you cannot then deselect a row or a column (with
<Ctrl> select). There are different structures and exposed attributes for UNO
actions to affect.

These misconceptions of a shared data structure and function lead to issues
like bug 37223.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Libreoffice-ux-advise mailing list