Bug 105550 - times don't respect am and pm in "New Event" window
Summary: times don't respect am and pm in "New Event" window
Status: RESOLVED DUPLICATE of bug 55334
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Reinhold Kainhofer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-12 19:06 UTC by Charles Samuels
Modified: 2005-07-25 05:36 UTC (History)
0 users

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 Charles Samuels 2005-05-12 19:06:54 UTC
Version:           3.4 (using KDE 3.4.89 (CVS >= 20050314), compiled sources)
Compiler:          gcc version 3.3.6 (Debian 1:3.3.6-1)
OS:                Linux (i686) release 2.6.10

my KDE is configured to use the following time format:
"pH:MM:SS" (notice how I use 12 hour time without the "am/pm"?)

This is because I can't count past 12 :)

In the combobox, if I select (for example) 11:00-12:00, it thinks I mean 11:00am to 12:00am (midnight) and thus thinks I selected an impossible range.

I think the following system should work:
- Always show the AM/PM if the time format is set to "pH"
- If the "end time" is before the "begin time", assume there's a PM

thanks
Comment 1 Andy 2005-06-30 14:43:26 UTC
I have the exact same problem with New Events & To-Dos. The only thing you can do to set the time past noon is go to the Calendar view and drag the event box to the correct time. This has been a bug for quite sometime and I always figured somebody knew about it and was going to fix it. But I guess nobody switches the time format  like we did.

The dropbox just needs to correctly display the times with AM/PM suffixes. The problem where the person selected an impossible range, I think it means the time is carried over to the next day.
Comment 2 Reinhold Kainhofer 2005-06-30 15:01:47 UTC
On Thursday 30 June 2005 14:43, Andy wrote:
> I have the exact same problem with New Events & To-Dos. The only thing you
> can do to set the time past noon is go to the Calendar view and drag the
> event box to the correct time. This has been a bug for quite sometime and I
> always figured somebody knew about it and was going to fix it. But I guess
> nobody switches the time format  like we did.
>
> The dropbox just needs to correctly display the times with AM/PM suffixes.


Sure, but you explicitly configured KDE to *NOT* show the am/pm suffixes, so 
honestly, what do you expect?

Cheers,
Reinhold
Comment 3 Andy 2005-07-07 18:21:47 UTC
Ah ok it works if you switch the time format to "pH:MM:SS AMPM". Thanks
Comment 4 Charles Samuels 2005-07-07 18:52:37 UTC
> Sure, but you explicitly configured KDE to *NOT* show the am/pm suffixes, so 
> honestly, what do you expect? 

I expect things to work when they appear in the UI.

At least clicking on something in the list should work, but it does not. All you have to do is go by its position in the list.  I should improve time parsing in there, it's seems extremely constrained.  KSpread's isn't too good either
Comment 5 Andy 2005-07-08 14:41:37 UTC
Now I remember why I turned off AM/PM suffixes for the time format in the first place when I started using KDE 2 years ago! Because now everything with the time takes up more space (the panel clock, date fields in kmail, etc). So I would like to renew my request that the dropdown works even without AM/PM. Thank you in advance.
Comment 6 Reinhold Kainhofer 2005-07-24 21:17:33 UTC
It's not possible to make it work like you . Imagine you select 2:00 (pm) from the list. Now simply enter "1" in front, so you  end up with 12:00. Is that now supposed to be am or pm?

If you don't want the am/pm, you need to use 24-hour format to make the interpretation of the input unique, otherwise certain things won't work (korganizer, kalarm, in short, everything where you need to enter a time).

We've had this discussion already a few times, and it is and stays a configuration problem. There needs to be a unique interpretation of each time string, relying on other things (like which item was selected, then edited) isn't going to work.

We have the same issue also with dates when the year is written in two-digits. E.g. what does a birthday of 01/01/05 mean? Jan 1, 2005? Or 1905?
The request to have two formats is in bug 55334.

Cheers,
Reinhold

*** This bug has been marked as a duplicate of 55334 ***
Comment 7 Charles Samuels 2005-07-25 05:36:39 UTC
Well, if it even accepted 24 hour formats, that'd be nice.

You shouldn't allow it to be configurable such that everything breaks!

-Charles