Bug 261206 - Show signs and the numbers while doing operations.
Summary: Show signs and the numbers while doing operations.
Status: RESOLVED DUPLICATE of bug 144741
Alias: None
Product: kcalc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-25 08:33 UTC by mindentropy
Modified: 2010-12-25 15:23 UTC (History)
0 users

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 mindentropy 2010-12-25 08:33:22 UTC
Version:           2.7 (using KDE 4.5.1) 
OS:                Linux

1) When I press -5 kcalc doesn't show signs. This used to work in the previous version of kcalc. 
2)Also what happened to numbers being shown in the display. When I type of "6-5" I would prefer it to be shown in the display till I press the '=' button. This used to happen in the previous kcalc I think. Also please make the display editable to correct mistakes in calculations.

Reproducible: Always

Steps to Reproduce:
1) Type -5. No sign display. Leading to doubts of whether you pressed the sign.
2) Type 6-5. No numbers displayed.

Actual Results:  
1) Type -5. No sign displayed. Leading to doubts of whether you pressed the sign.
2) Type 6-5. No numbers displayed.

Expected Results:  
1) No sign displayed
2) No numbers displayed
Comment 1 Christoph Feck 2010-12-25 15:23:36 UTC
You are probably confusing KCalc with another calculator program. KCalc has always worked like a traditional calculator, where only one number is displayed. Additionally, to enter negative numbers, you have to press the "+/-" (change sign) key after entering the significant digits of the number.

There are already other wishes files to modernize KCalc's interaction mode, for example to support entering complete lines (see bug 77158, bug 144741) so I am closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 144741 ***