Bug 353666 - Regression: using a different background colour for occupied days seems no longer to work
Summary: Regression: using a different background colour for occupied days seems no lo...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: agendaview (weekview) (show other bugs)
Version: 5.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-07 20:11 UTC by Christian (Fuchs)
Modified: 2018-01-31 17:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the issue (101.74 KB, image/png)
2015-10-07 20:11 UTC, Christian (Fuchs)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2015-10-07 20:11:09 UTC
There is a setting to have days that are blocked by appointments to be shown in a different colour. This setting seems to no longer have an effect on KF5 based korganizer

Reproducible: Always

Steps to Reproduce:
1. create a new appointment
2. set it to be for the whole day
3. set it to block you for other appointments
4. configure the background to be different for such days

Actual Results:  
No difference

Expected Results:  
Different colour is used
Comment 1 Christian (Fuchs) 2015-10-07 20:11:37 UTC
Created attachment 94880 [details]
Screenshot showing the issue

Screenshot showing the issue
Comment 2 Denis Kurz 2017-06-23 20:21:37 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:39 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.