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

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=90883

Jay Philips <philipz85 at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=90
                   |                            |882
         Resolution|DUPLICATE                   |---
     Ever confirmed|0                           |1
         Whiteboard|                            |needsDevEval topicUI

--- Comment #3 from Jay Philips <philipz85 at hotmail.com> ---
Reopening as bug 90821 doesnt cover what this enhancement intends to fix.

(In reply to V Stuart Foote from comment #1)
> @Jay, hate to state the obvious, but Calc's cells/columns/rows have no data
> structure in common with Table's cells/columns/rows.

I'm quite aware that they dont. ;D

> 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.

I believe it will be possible. We can detect when an entire row is selected, as
you can see it in the statusbar, so using the same information, we should be
able to change the behaviour of the uno commands to insert accordingly.

> 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).

Not saying that it should, but i'm suggesting that unifying the behaviour means
that its easier for users to have a consistent experience between the apps.

> 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.

I'm aware of this, which is why i have asked that alternative insert uno
commands be created for writer which have the similar insertion direction
behavior (bug 90882).

Another problem is that these same named uno commands have the single icons to
them when they have different behaviours, which also causes more problems.

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