Date: prev next · Thread: first prev next last
April 2015 Archives by date, by thread · List index


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |vstuart.foote@utsa.edu
          Component|Calc                        |ux-advise
     Ever confirmed|0                           |1
           Severity|normal                      |enhancement

--- Comment #4 from V Stuart Foote <vstuart.foote@utsa.edu> ---
As Calc sheets/cells/rows/columns are completely different data objects to
Writer table/cells/rows/columns there is nothing wrong or unexpected with the
current state of the UI.

One can make an argument for UI enhancement that the cell/row/column selection,
insertion, and deletion should respond the same between Cells and Tables--the
fact that we use the same .uno command names and icons just strengthens the
argument for consistent behavior.

But folks should be aware that would require considerable rework of either
Tables or Sheets or both to bring them in line.

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.