https://bugs.kde.org/show_bug.cgi?id=501297
Alexander Semke <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED --- Comment #2 from Alexander Semke <[email protected]> --- (In reply to Jürgen Liebmann from comment #0) > Hi, > i have detected a strange behavior of labplot in the area of datetime: > In a spreadsheet with a column with format datetime the input of > 2024-03-31 01:55:00 is accepted > The input of 2024-03-31 02:00:00 is r converted to 2024-03-31 03:00:00 > 2024-03-31 02:00:15 in 2024-03-31 03:00:15 and so on. > This happen on all values between 2024-03-31 02:00:00 and 2024-03-31 > 02:59:59, > Haven't any guess why this happens. The datetime value is a bigint value of > milliseconds since 1970 or so. > > Good luck for bug hunting! The behavior is correct. On 2024-03-31, the local time 02:00:00-02:59:59 does not exist due to DST transition (clocks jump from 01:59:59 to 03:00:00). LabPlot follows Qt's standard DST handling, which auto-corrects invalid times to the next valid time. This prevents storing non-existent datetime values. This is consistent with Excel, Google Sheets, and most datetime libraries. Times like 01:55:00 and 03:00:00 work fine because they exist in the local timezone. -- You are receiving this mail because: You are watching all bug changes.
