Bug 179157 - Moving an event does a copy instead of a move
Summary: Moving an event does a copy instead of a move
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 179435 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-30 18:17 UTC by Geert Poels
Modified: 2009-02-15 13:03 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Geert Poels 2008-12-30 18:17:57 UTC 
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Using KOrganiser 4.1.0 :
Create an event, do a drag to another day, select move.
See how the event got copied, not moved.

Seems like this one is happening again : 
https://bugs.kde.org/show_bug.cgi?id=35163
Comment 1 FiNeX 2008-12-31 11:50:09 UTC 
This bug has been fixed on current trunk.
Comment 2 FiNeX 2008-12-31 11:59:32 UTC 
Sorry, I've misunderstand the original report, this is how to reproduce it:

1. Go to week view;
2. Make an event;
3. Move the event to another day;
4. Press the next week arrow;
5. Press the previous week arrow
Comment 3 Sergio Martins 2009-01-02 16:56:48 UTC 
SVN commit 904595 by smartins:

Fix event duplication when moving events with the mouse.

BUG: 179157


 M  +7 -1      koagendaview.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=904595
Comment 4 Sergio Martins 2009-01-03 01:38:25 UTC 
*** Bug 179435 has been marked as a duplicate of this bug. ***
Comment 5 Geert Poels 2009-02-15 09:25:52 UTC 
Hello, today I received the 4.1.4 KDE package in Ubuntu
The bug still exists !

1. Make an event
2. Move it to another day (drag n drop, select move)
-> a copy is made, not a move !

Supplementary :
3. Delete the old event : the new one is gone too !!
Comment 6 FiNeX 2009-02-15 12:33:53 UTC 
@Geert: stop at step 2, close korganizer and reopen it, what is the result?
Comment 7 Geert Poels 2009-02-15 12:57:02 UTC 
They are as they should be !
So it seems the original one isn't cleaned up (visually)
Comment 8 FiNeX 2009-02-15 13:03:44 UTC 
It was a refresh problem on 4.1.x. It is no more reproducible on current trunk (and, if I remember correctly) it should be fixed in 4.2 too.