Bug 305211 - Events and tasks width or height aren't correctly set when there are some time conflicts
Summary: Events and tasks width or height aren't correctly set when there are some tim...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: agendaview (weekview) (show other bugs)
Version: 4.13
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-15 18:28 UTC by Alexandre Bonneau
Modified: 2017-01-08 19:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Wrong layout in the bottom part of the agenda view (5.49 KB, image/png)
2012-08-15 18:28 UTC, Alexandre Bonneau 		Details
Wrong layout in the upper part of the agenda view (19.16 KB, image/png)
2012-08-15 18:29 UTC, Alexandre Bonneau 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Bonneau 2012-08-15 18:28:10 UTC 
Events and tasks width or height aren't correctly set when there are some time conflicts. It's hard to explain with words, so please take a look at the attached screen captures.

On the first one, the orange task should take half the width of the day, on the second one, it's an hard one, but 'Test 3' and 'Test 1' shouldn't look like that imho.

Reproducible: Always
Comment 1 Alexandre Bonneau 2012-08-15 18:28:48 UTC 
Created attachment 73193 [details]
Wrong layout in the bottom part of the agenda view
Comment 2 Alexandre Bonneau 2012-08-15 18:29:07 UTC 
Created attachment 73194 [details]
Wrong layout in the upper part of the agenda view
Comment 3 Denis Kurz 2016-09-24 18:45:47 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:19:27 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.
Comment 5 Alexandre Bonneau 2017-01-08 19:42:30 UTC 
To be continued on #374772