Bug 156487 - Default appointment time is not used when creating a new event in month view
Summary: Default appointment time is not used when creating a new event in month view
Status: RESOLVED INTENTIONAL
Alias: None
Product: korganizer
Classification: Applications
Component: monthview (show other bugs)
Version: 3.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-01-23 18:20 UTC by Aurelien Bompard
Modified: 2012-07-06 20:35 UTC (History)
3 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 Aurelien Bompard 2008-01-23 18:20:55 UTC
Version:           3.5.8-11.svn20080109.ent (using KDE 3.5.8)
Installed from:    Fedora RPMs
Compiler:          GCC 4.1.2 
OS:                Linux

When a default appointment time is set in Settings > Configure Korganizer > Date & Time > Default appointment time, it is not used for new events.
For new events, the "time associated" checkbox is off by default, and the time is 00:00 to 02:00. This does not change when unchecking the box.
I've tried this on a new user account, and on another box which has korganizer 3.5.7. Both are from the "enterprise branch".
Comment 1 Roman Fietze 2008-03-07 21:45:01 UTC
Still true for 3.5.9 from OpenSUSE 10.3 RPMs. Bute here it is only true for every view except month view, in the month view the default seems to be an all day event.
Comment 2 Michael Leupold 2008-09-28 16:38:46 UTC
On trunk r865573 new events in the month-view are assumed to be all-day events, defaults are used properly for all other views. I think this bug is fixed.
Comment 3 Sergio Martins 2009-03-04 02:06:05 UTC
The Default Event time is only used if you create a new event through the tool bar or through the menu.
Comment 4 Allen Winter 2012-07-06 20:35:21 UTC
yep, i even looked at Google calendar and it also creates new events by default as "all day" in month view.

i'm not 100% sure if I agree with this behavior,  but it seems to be a "standard" amongst calendar apps.  so let's mark this resolved.