Bug 201200 - Jumps back to today after editing
Summary: Jumps back to today after editing
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.2.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-23 10:36 UTC by Michael Holtermann
Modified: 2017-01-07 22:32 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 Michael Holtermann 2009-07-23 10:36:33 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Hi,

in month view, after making any change to an event, like creating a new event or deleting an old one or even "toggle reminder" from context menu, the cursor jumps back to today. 

The expected behavior is to hold the current position.

This works correctly in day and week views.

This is very unhandy if you like to edit more than one event.

Thanks in advance!
Greetings, Michael.
Comment 1 Michael Holtermann 2009-07-24 14:56:12 UTC
additional note: If I copy an event from one day to another, it is placed on today.

1. Select an event
2. Press Ctrl+C
3. Click on another day
4. Either press Ctrl+V or context menu --> paste
--> Event is placed on today.

Greetings, Michael.
Comment 2 Denis Kurz 2016-09-24 18:46:14 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 Michael Holtermann 2016-09-24 18:49:57 UTC
Sorry, I haven't used KOrganizer for some years now, and could not provide any updates.
Comment 4 Denis Kurz 2017-01-07 22:32:59 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.