Bug 177048

Summary:	Make cashew an option that can be disabled
Product:	[Unmaintained] plasma4	Reporter:	kgw
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	aseigo, godutchnow, idonoteverreadthis, illumilore
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kgw 2008-12-06 11:29:01 UTC

Version:            (using Devel)
Installed from:    Compiled sources

As I use a completely empty desktop when editing a picture (the only way to have my screen not tamper with the colour calibration, I need to disable the cashew completely as otherwise there will be a segment of my LCD which has different contrast settings and colour reproduction due to the contrast optimisation of the screen kicking in. 
So make the cashew an option that can be completely disabled.

Comment 1 Aaron J. Seigo 2008-12-06 22:24:30 UTC

the cashew is not going to be made an *option*. you can switch to a different Activity that doesn't have one (some distributions ship with such a thing already).

what kind of automatic colour calibration does your screen do, anyways, that a few grey pixels in the corner changes it?

Comment 2 kgw 2008-12-06 23:04:11 UTC

It is an LG wide colour gamut screen with an high contrast optimization that changes back lighting in segments according to the contents of that segment and those measly grey bits do make quite a difference and mess up the black point in that screen segment. Tell me an activity that doesn't have this and I will never switch back!

Comment 3 Aaron J. Seigo 2008-12-06 23:16:07 UTC

Blank Desktop for one, Suse also have a straight desktop containment.

Comment 4 FiNeX 2009-08-04 20:53:19 UTC

*** Bug 189887 has been marked as a duplicate of this bug. ***

Comment 5 Jonathan Thomas 2010-08-23 16:51:37 UTC

*** Bug 248796 has been marked as a duplicate of this bug. ***

Comment 6 Christoph Feck 2011-08-05 23:40:47 UTC

*** Bug 279237 has been marked as a duplicate of this bug. ***