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.
(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
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.
(In reply to Mike Kaganski from comment #1)
> there is Ctrl+=
FTR: The drop-down was added in bug 120697.
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).
That’s pretty clunky.
(In reply to Mike Kaganski from comment #2)
> (In reply to Mike Kaganski from comment #1)
> > there is Ctrl+=
> Sorry, Alt+=
(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
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).
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.
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 ;-)
(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.
(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.
The topic was on the agenda of the design meeting but didn't receive further input. So let's do as suggested.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
*** Bug 154621 has been marked as a duplicate of this bug. ***