this post was submitted on 10 Jun 2024
-8 points (36.7% liked)

KDE

5056 readers
55 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
 

omg KDE @kde if it ain't broken, fix it until it is?

#KDE #FeatureCreep

you are viewing a single comment's thread
view the rest of the comments
[–] mox@lemmy.sdf.org 2 points 3 months ago* (last edited 3 months ago) (3 children)

I don't know what this image is supposed to tell us, but I can confirm that KCalc behaves badly in some common situations. (At least, it does in Plasma 5.) Want to see an example?

Put it in Simple Mode, and try copying and pasting various multi-digit numbers with leading zeroes. Some of them work fine. Others, like 054 and 009, yield surprising results.

Spoiler:054 becomes 44
009 becomes nan

A programmer or mathematician might be able to deduce that KCalc is trying to interpret those numbers as octal (base 8 instead of base 10), if they're paying close attention. That doesn't help anyone who is just trying to total a bunch of numbers from a document, using their default desktop calculator, and doesn't notice a misinterpreted value along the way. Their total will just be wrong, or in the case of nan, they will just be frustrated that the calculator doesn't work.

This behavior is probably not appropriate for Simple Mode.

It does the same thing even in Numerical System Mode with decimal (base 10) explicitly selected, which is absolutely not appropriate.

[–] tobozo@mastodon.social 0 points 3 months ago (2 children)

@mox wow that's even worse than losing continuity for the sakes of that new history feature (using Kcalc version 24.05.0)

here's what I did before getting the input error:

2*2 [enter]

*2 [enter]

I was expecting to read "8" but got "input error" instead

[–] mox@lemmy.sdf.org 1 points 3 months ago* (last edited 3 months ago) (1 children)

I followed your steps and got 8 in KCalc 22.12.3.

Perhaps you found a bug in your version? You can search for existing bug reports, or create new ones, here: https://bugs.kde.org/