Bug 322672 - Task items unreadable in agendaview
Summary: Task items unreadable in agendaview
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: agendaview (weekview) (other bugs)
Version First Reported In: 4.10.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-22 09:14 UTC by Stefan Kebekus
Modified: 2017-01-07 22:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Image that shows unreadable items (305.51 KB, image/png)
2013-07-22 09:20 UTC, Stefan Kebekus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Kebekus 2013-07-22 09:14:16 UTC
Depending on the number of whole-day tasks and events and on their distribution over days of the week, the tasks and events are not shown properly.  Whenever I add a task or event that leads to problems (which happens for every 10-20th whole-date event that I add), the agendaview starts to blink rapidly. When I go to a week where the problem does not occur and then go back, the blinking has stopped, but the items overlap, making them impossible to read.

Reproducible: Always

Steps to Reproduce:
1. Add whole-day tasks and items as shown in the screenshot that I will add in a second
2. Open agendaview if not already open
Actual Results:  
Flickinering and unreadable items

Expected Results:  
No flicker, readable items.
Comment 1 Stefan Kebekus 2013-07-22 09:20:57 UTC
Created attachment 81258 [details]
Image that shows unreadable items
Comment 2 Denis Kurz 2016-09-24 18:45:29 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 Denis Kurz 2017-01-07 22:14:15 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.