Bug 489339 - Using decimals without a leading zero causes input error and not carrying output to inputs
Summary: Using decimals without a leading zero causes input error and not carrying out...
Status: RESOLVED DUPLICATE of bug 487566
Alias: None
Product: kcalc
Classification: Applications
Component: general (show other bugs)
Version: 24.05.1
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-27 21:39 UTC by irongrinder
Modified: 2024-06-29 06:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Errors labels respective to report (38.80 KB, image/png)
2024-06-27 21:39 UTC, irongrinder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description irongrinder 2024-06-27 21:39:37 UTC
Created attachment 171103 [details]
Errors labels respective to report

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
A) As title states, Kcalc givers "Input Error" if you don't add a leading zero to a decimal number. It should probably just inject a leading 0 if a decimal doesn't contain one.

B) There's also an issue of it does not automatically using the output at the first number in a new equation if the user enters a mathematical symbol that may or may not be related to the issue.

STEPS TO REPRODUCE
A) 1. Enter 1+.5 and hit enter

B) 1. Enter 2+2 and hit enter
     2. Enter +2 and hit enter

OBSERVED RESULT
A) Input error

B) 2

EXPECTED RESULT
A) An output of 1.5

B) 6
Comment 1 Gabriel Barrantes 2024-06-27 22:33:27 UTC
Duplicate of 487566 & 487659
Comment 2 Christophe Marin 2024-06-29 06:11:06 UTC
(In reply to Gabriel Barrantes from comment #1)
> Duplicate of 487566 & 487659

Let's use the correct resolution then

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