Bug 222599

Summary:	Time, date and duration default values in the 'New Event' dialogue are not handy.
Product:	[Applications] korganizer	Reporter:	Sabine Faure <sabine>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, smartins
Priority:	LO
Version:	4.3
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Sabine Faure 2010-01-13 22:29:00 UTC

Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch Kontact and go to KOrganizer
- Click on the 'New Event' button
- Select My Data/Agenda (Akonadi ressource)
- Enter a title and location for the new event
- The default start time is 10:00, the default end time is 12:00 and the default duration is 2 hours.
- Try to change the start time to 22:10

You cannot use the arrow list since there is only 22:00 or 22:15 available from it.
I think it would be a lot quicker to just have + and - buttons instead of a list.

- Now click in the start time zone and edit the start time manually.
- The end time changes automatically to the next day at 00:10

This forces the user to edit both the end time and end date who wanted to end the event at 22:35. This is not efficient.
Maybe a solution would be to make the duration time editable so that all this information could be changed in one go.

Akonadi-ports branch, Svn Rev 1074068

Comment 1 Laurent Montel 2010-02-01 11:55:08 UTC

It's right it's not very "ergonomique"
But in config dialogbox in time/date you can change default duration etc.

Comment 2 Denis Kurz 2016-09-24 18:52:43 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:41:54 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.