Bug 393214

Summary:	Putting a decimal separator prevents data from entering into a spreedsheet
Product:	[Applications] LabPlot2	Reporter:	urcindalo
Component:	general	Assignee:	Alexander Semke <alexander.semke>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:	https://commits.kde.org/labplot/386e4b102cb7f9d1147598c7ad757e5963326f30	Version Fixed/Implemented In:	2.5
Sentry Crash Report:

Description urcindalo 2018-04-17 08:15:55 UTC

When entering data into a spreedsheet, labplot-2.5.0 does not honor my numeric format setting. Since I’m a Spaniard, I have my KDE 5 configured to enter decimals with a “,”. However, no matter how I enter a decimal number (2,3 or 2.3, for instance), the number is simply ignored after pressing enter, as if I had not entered anything. BUT, if I just enter a number with no decimal places or I use a power, like 23e-1, then I get a correct 2,3 in the cell (yes, lablot 2.5.0 then chooses the comma to show the decimal separator).

Comment 1 Alexander Semke 2018-04-17 16:14:29 UTC

Git commit 386e4b102cb7f9d1147598c7ad757e5963326f30 by Alexander Semke.
Committed on 17/04/2018 at 16:13.
Pushed by asemke into branch 'master'.

Correctly evaluate the current locale when doing data entry in the spreadsheet.
FIXED-IN: 2.5

M  +2    -1    src/backend/spreadsheet/SpreadsheetModel.cpp

https://commits.kde.org/labplot/386e4b102cb7f9d1147598c7ad757e5963326f30

Comment 2 Alexander Semke 2018-04-17 16:15:34 UTC

(In reply to urcindalo from comment #0)
> When entering data into a spreedsheet, labplot-2.5.0 does not honor my
> numeric format setting.
Thanks for reporting this! Can you please pull the current code and try again?

Comment 3 urcindalo 2018-04-17 16:46:20 UTC

(In reply to Alexander Semke from comment #2)
> (In reply to urcindalo from comment #0)
> > When entering data into a spreedsheet, labplot-2.5.0 does not honor my
> > numeric format setting.
> Thanks for reporting this! Can you please pull the current code and try
> again?

Thanks very much indeed!
It seems fixed :)