Bug 224704 - Display problem when two events are dragged and dropped to overlap
Summary: Display problem when two events are dragged and dropped to overlap
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.3
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 00:14 UTC by Sabine Faure
Modified: 2017-01-07 22:06 UTC (History)
2 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 Sabine Faure 2010-01-29 00:14:09 UTC 
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KOrg
- Create two new events (Event 1 from 10:00 to 12:00 and Event 2 from 13:00 to 15:00)
- drag and drop Event 2 so that it now starts at 11:00

Both events are displayed one on top of the other and they keep blinking so that only part of each event is constantly readable.

Whereas normally overlapping events should be displayed one next to the other, each event taking half the width of the agenda view.
Which end up to be the case if you quit and relaunch KOrg: Event 1 and Event 2 are now displayed one next to the other in the Agenda view.

Trunk, Svn Rev 1081581
Comment 1 Sergio Martins 2010-09-07 12:01:13 UTC 
The usual blinking, but it's ok.
Comment 2 Alexandre Bonneau 2012-01-31 19:12:30 UTC 
Except it uses 100% of a CPU while it blinks :/
Comment 3 Denis Kurz 2016-09-24 18:43:15 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 4 Denis Kurz 2017-01-07 22:06:21 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.