Bug 150262 - Make Autosum button a split button
Summary: Make Autosum button a split button
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyMedium, easyHack, skillCpp
: 154621 (view as bug list)
Depends on:
Blocks: Calc-Formula-Bar
  Show dependency treegraph
 
Reported: 2022-08-04 12:18 UTC by MartinP
Modified: 2023-04-05 12:32 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MartinP 2022-08-04 12:18:06 UTC
FORMCONTROLS

Performing a summation of a column of numbers is arguably the most common calculation carried out in a spreadsheet.

Unless I am mistaken the quickest (least clicks) way to do this mouse only is to highlight the column of numbers, hit the sigma dropdown and select "Sum". Bearing in mind that sigma means add I think that should be the default. I'd say one click of sigma to perform an addition. Should the user want min, max etc then they can subsequently select the alternate function from the sigma drop down.
Comment 1 Mike Kaganski 2022-08-05 07:51:14 UTC
(In reply to MartinP from comment #0)
> the quickest (least clicks) way to do this mouse only
> is to highlight the column of numbers, hit the sigma dropdown and select
> "Sum".

No.
As explained in https://wiki.documentfoundation.org/ReleaseNotes/7.0#Other, since 7.0, there is Ctrl+=, which allows you to put cursor under the column (or select the range), and use the shortcut.
Comment 2 Mike Kaganski 2022-08-05 07:51:46 UTC
(In reply to Mike Kaganski from comment #1)
> there is Ctrl+=

Sorry, Alt+=
Comment 3 Mike Kaganski 2022-08-05 08:04:38 UTC
FTR: The drop-down was added in bug 120697.
Comment 4 Mike Kaganski 2022-08-05 08:19:26 UTC
IMO, a very natural and reasonable request.

The code pointer (if UX agrees) is commit 0ec98930888ee9f29032d12185baefc71da8489f itself; it had removed a code for a simple button click, and introduced the drop-down code, changing the button's type from ToolBoxItemBits::NONE into ToolBoxItemBits::DROPDOWNONLY. To fix this, one would need to make it ToolBoxItemBits::DROPDOWN, restore the simple click code, and make it conditional on what was the last used operation. Indeed, the drop-down code needs to update the last-used function.

The persistence of the last used operation could be per-session (the easiest), or stored in the profile (then a mew option needs to be added for that).
Comment 5 MartinP 2022-08-05 08:23:57 UTC Comment hidden (off-topic)
Comment 6 Mike Kaganski 2022-08-05 08:40:46 UTC
(In reply to Mike Kaganski from comment #4)
> and make it conditional on what was the last used
> operation. Indeed, the drop-down code needs to update the last-used function.
> 
> The persistence of the last used operation could be per-session (the
> easiest), or stored in the profile (then a mew option needs to be added for
> that).

Or maybe even make the main button to execute SUM always; that would be even easier implementation-wise, and also not requiring to change button icon dynamically (and having new icons for that).
Comment 7 Heiko Tietze 2022-08-05 08:45:46 UTC
So you suggest to revert bug 120697 in order to have one "sigma" button to just calculate the sum with one instead of two clicks? Sounds wrong to me.
Comment 8 Heiko Tietze 2022-08-05 08:47:37 UTC
Guess you mean a split button with a default action and some other in the menu. Reasonable although more complex. Maybe Martin is happy with the keyboard shortcut. And users might become greedy asking to have the last used action as the default ;-)
Comment 9 Mike Kaganski 2022-08-05 08:58:59 UTC
(In reply to Heiko Tietze from comment #7)
> So you suggest to revert bug 120697 in order to have one "sigma" button to
> just calculate the sum with one instead of two clicks?

Surely no; if you reply to comment 6, then the "main button" (in addition to the overall "make it a split button" topic) implies there's something else (the drop-down) besides the *main* part. So - your comment 8.

(In reply to Heiko Tietze from comment #8)
> Maybe Martin is happy with the keyboard shortcut.

Oh, see comment 5. And don't let me started about users considering keyboard shortcuts "clunky"; but that's life.
Comment 10 Mike Kaganski 2022-08-05 09:01:04 UTC
(In reply to Heiko Tietze from comment #8)
> although more complex

Note that it basically needs to restore one function from the state before bug 120697 (the one that was executed when the button was pressed), and change the button type to ToolBoxItemBits::DROPDOWN. As easy as that.
Comment 11 Heiko Tietze 2022-08-11 13:33:19 UTC
The topic was on the agenda of the design meeting but didn't receive further input. So let's do as suggested.
Comment 12 QA Administrators 2023-02-08 03:24:50 UTC Comment hidden (obsolete)
Comment 13 Mike Kaganski 2023-04-05 12:32:46 UTC
*** Bug 154621 has been marked as a duplicate of this bug. ***