Bug 224807 - Display problem when resizing or drag and dropping an event.
Summary: Display problem when resizing or drag and dropping an event.
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 19:58 UTC by Sabine Faure
Modified: 2017-01-07 21:48 UTC (History)
1 user (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 Sabine Faure 2010-01-29 19:58:05 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KOrg
- Create two new events for today (Event 1, 14:00 - 16:00 and Event 2, 19:00 - 21:00)
- They should be displayed correctly in the agenda view.
- Now Resize Event 1 so that it ends at 17:00. To do so click on the bottom edge of the event and drag it to 17:00 while holding the mouse button.

When you release the mouse button the background color gets darker in Event 1 first and switches back to normal and then Event 2 disappears and reappears very quickly eventhough Event 2 was not modified at all.

The same thing happens when releasing the mouse button after drag and dropping an event (background becomes darker and then switches back to normal and other events from the same day blinks eventhough there were not modified).

Trunk, Svn Rev 1082000
Comment 1 Denis Kurz 2016-09-24 18:46:48 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 2 Denis Kurz 2017-01-07 21:48:08 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.