Bug 85349 - numbers for start/end in edit-event-dialog interpreted as 0:xx
Summary: numbers for start/end in edit-event-dialog interpreted as 0:xx
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.2.1
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 91396 171189 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-07-16 21:37 UTC by fuqnbastard
Modified: 2021-05-11 02:44 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fuqnbastard 2004-07-16 21:37:35 UTC
Version:           3.2.1 (using KDE 3.2.2, Gentoo)
Compiler:          gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.5-gentoo

In the "Edit Event" dialog: When I enter pure numbers (like "12") in the start/end time text edit controls, they are interpreted as 0:<number>. What I'd expect and want is <number>:00.
Comment 1 Reinhold Kainhofer 2004-10-25 19:45:02 UTC
Thanks for the bug report. You are probably right about the 12, but the problem here is that you can also enter times without the ':', e.g. 615 meaning 
6:15. Now how would you then interpret 0012 ? You just enter a number, so 0012=12 (unless we parse the string manually, which will include another bunch of problems), which according to your wish 12=12:00... That's the other side of the coin.

Reinhold
Comment 2 Reinhold Kainhofer 2004-10-25 19:45:22 UTC
*** Bug 91396 has been marked as a duplicate of this bug. ***
Comment 3 Reinhold Kainhofer 2006-11-02 19:35:43 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 Sergio Martins 2009-03-06 05:50:26 UTC
*** Bug 171189 has been marked as a duplicate of this bug. ***
Comment 5 Sergio Martins 2009-03-06 05:51:19 UTC
A config setting to choose the behaviour would be useful.
Comment 6 Dotan Cohen 2009-03-06 14:40:25 UTC
> Now how would you
> then interpret 0012?

I would interpret "0012" as 00:12, distinct from "12" which would be 12:00. I understand that there is a technical difficulty of distinguishing 0012 from 12 however the user should not be concerned with such technical difficulties. You could treat the input field as text instead of as an integer, and deal with it that way. As a user, that technical detail does not concern me.

But really, how often does one make an appointment for the hours 0:00 - 0:59 anyway? While it technically should be possible, it is obvious that it is far less common to make appointments for those hours than it does for standard waking and business hours. Therefore the default behaviour should be to assume that "12" would be "1200". One can still enter military time if he likes, and "12" is _not_ military time for either "1200" or for "0012". Just check if the input is less than 100, if it is, then multiply by 100. The rare occasion in which someone needs to make an appointment at the hours 00:01 - 00:59 can be dealt with by actually typing 00:12 with a colon.
Comment 7 gjditchfield 2021-05-11 02:44:08 UTC
With the KF5 time widget, the hour and minute fields are entered separately, so this problem doesn't arise.