[Libreoffice-ux-advise] [Bug 143962] EDITING range reference should update when edge cell is moved in same column (drag and drop or cut and paste)

2023-11-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143962

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
   Keywords|needsUXEval |

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

[Libreoffice-ux-advise] [Bug 143962] EDITING range reference should update when edge cell is moved in same column (drag and drop or cut and paste)

2023-05-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143962

--- Comment #7 from Eike Rathke  ---
Makes sense _iff_ the move is in the same direction as the range span, e.g.
moving (drag) top cell(s) further up or down (not below the bottom row),
and not elsewhere.

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

[Libreoffice-ux-advise] [Bug 143962] EDITING range reference should update when edge cell is moved in same column (drag and drop or cut and paste)

2023-05-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143962

--- Comment #6 from Heiko Tietze  ---
(In reply to laurent combe from comment #1)
> Created attachment 17 [details]
> file to show the bug reported

=B5+B6+B7+B8+B9 vs. =SUM(C5:C9)

We update individual cells but keep the range while Excel also changes the
range to C3:C9. The difference is if C4 contains a value: Excel will add it to
the equation, we not.

I tend to disagree with Excel's workflow but user expect similar behavior.

Some limits exist in that pasting below the SUM function or in columns left or
right has no effect on the range.

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

[Libreoffice-ux-advise] [Bug 143962] EDITING range reference should update when edge cell is moved in same column (drag and drop or cut and paste)

2023-05-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143962

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||needsUXEval

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

[Libreoffice-ux-advise] [Bug 143962] EDITING range reference should update when edge cell is moved in same column (drag and drop or cut and paste)

2023-05-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143962

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Version|unspecified |Inherited From OOo
   Severity|normal  |enhancement
Summary|EDITING Address error when  |EDITING range reference
   |move (drag and drop) a  |should update when edge
   |range   |cell is moved in same
   ||column (drag and drop or
   ||cut and paste)
 Blocks||108253
 CC||er...@redhat.com,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=75
   ||904

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
Reproduced in OOo 3.3 and a recent master build.

I can confirm that in Excel 365, following the same steps, the range is
extended in the C10 formula. However, the range is not updated if the cell is
dragged to a different column, or if it is dragged below the original range. So
this seems to only happen in specific, straight-forward cases.

Other apps:
- OnlyOffice does not extend the range, same as LibreOffice
- Gnumeric and Google Sheets extend the range, same as Excel

I consider this as request for enhancement rather than a bug.

Eike and UX team, what are your thoughts on this?

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 002ae41bb6088002ba3ed0188ac822fb823a23f9
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108253
[Bug 108253] [META] Calc cell formula bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.