Bug 108473 - Repeated presses of the Enter key or equals button do not repeat the last calculation
Summary: Repeated presses of the Enter key or equals button do not repeat the last cal...
Status: CONFIRMED
Alias: None
Product: kcalc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 17.12
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords: junior-jobs, usability
: 185457 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-07-03 05:40 UTC by David Bowen
Modified: 2025-06-22 21:52 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Bowen 2005-07-03 05:40:11 UTC
Version:           1.8.1 (using KDE KDE 3.4.1)
Installed from:    Fedora RPMs
OS:                Linux

On some old fashioned real world calculators I've used the last calculation gets repeated each time I hit the equals sign. This is useful if you're converting from bytes to MB for example as you can just do "/1024" and hit equals twice. kcalc doesn't seem to do this and I'm not sure why - I suspect I'm missing something obvious here.
Comment 1 Rolf Viehmann 2005-07-14 18:47:28 UTC
Well, I'm not sure if you are missing something or not, but I also think this would be a good idea, easy to implement and useful. Also there could be a menu entry "repeat last operation" (with exactly the same function).
Comment 2 Jonathan Marten 2009-03-12 17:42:58 UTC
*** Bug 185457 has been marked as a duplicate of this bug. ***
Comment 3 jeremy9856 2015-05-28 22:24:29 UTC
I think it's a good idea to add this behavior but there have to be an option to disable it if needed
Comment 4 Christoph Feck 2018-08-16 22:28:23 UTC
Git commit 0c4c775b9dd36c3a93a707f28ff15232165b301a by Christoph Feck, on behalf of Maximilian Schiller.
Committed on 16/08/2018 at 22:26.
Pushed by cfeck into branch 'master'.

Repeat last action when pressing "=" or Enter

This patch allows to press the equal sign again in order to repeat
the last action again.

For example "5+10" yields "15" on Enter and if you press Enter or
equal sign again it repeats the "+ 10" by showing you "25" now.

This behavior is disabled by default and can be turned on in
KCalc's settings panel under "Misc".

Differential Revision: https://phabricator.kde.org/D12099

M  +10   -0    general.ui
M  +4    -0    kcalc.kcfg
M  +25   -1    kcalc_core.cpp
M  +4    -0    kcalc_core.h

https://commits.kde.org/kcalc/0c4c775b9dd36c3a93a707f28ff15232165b301a
Comment 5 David Bowen 2021-04-08 18:06:46 UTC
Thank you, it works as described and the setting is persisted so it keeps working the way I enjoy.
Comment 6 Yao Mitachi 2025-02-19 03:01:33 UTC
This has since been removed. I would like it restored, if possible, so that I can use the calculator like most physical calculators.
Comment 7 Andreas 2025-04-30 18:28:57 UTC
I agree. Why was this removed? This is an essential function for a basic calculator.
Comment 8 Marcel Partap 2025-04-30 21:43:59 UTC
(In reply to Andreas from comment #7)
> I agree. Why was this removed? This is an essential function for a basic
> calculator.

Seems not implemented (yet), big rewrite happened January 2024 in https://invent.kde.org/utilities/kcalc/-/commit/c7864e9547b2ef2e9e318a88c78ba51f10fbc5e3 ..
Comment 9 John Kizer 2025-05-09 04:52:48 UTC
I can reproduce this on KCalc 25.04.0
Comment 10 colin 2025-06-22 21:13:37 UTC
I can reproduce this issue / "bug" across Arch, Fedora, Debian, etc. 

When is this feature going to be implemented? 

The calculator in Windows has always worked this way. 
The calculator in Mac OS has always worked this way. 
Real-life calculators have always worked this way. 
I am stunned that this feature has not been implemented in Kcalc or actually ANY linux calculator that I've been able to find and test (except one..)
Funnily enough, KDE's plasma calculator widget DOES function / work this way! 

Can this PLEASE be brought to Kcalc?
Comment 11 Luigi Toscano 2025-06-22 21:52:09 UTC
I've changed the value of the "Version First Reported In" field to the oldest version available now (17.12), but it should have been  1.8.1. 
Please DON'T UPDATE the "Version First Reported In", because that field is meant to show against which version when the issue was originally created.