Bug 368201 - Desktop Effect Filter
Summary: Desktop Effect Filter
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: Other Other
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-03 16:52 UTC by andreas
Modified: 2017-01-03 00:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
kainz.a: Usability+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andreas 2016-09-03 16:52:09 UTC
In the desktop effect kcm you see by default all effects that are supported by the compositor and that are not internal effects. If you want to show also the not supported effects and the internal effects you have to "filter" to add them.

this is a bit confuse. I would suggest to change the behavior when you click on the edit button, you get
1. Desktop Effects
2. Internal Effects
3. Not supported Effects
4. Used Effects
5. All Effects

1. Desktop Effects show all Effects excluded 2. and 3.
4. show only the selected one
5. show ALL included 2. and 3.

and than the edit button will be changed to view-filter.

I think than this is more clear than some excluded filters.

Reproducible: Always
Comment 1 Martin Flöser 2016-09-04 08:07:54 UTC
Could you please elaborate what the advantage would be? Why would a user just want to see the unsupported effects for example?
Comment 2 andreas 2016-09-04 19:01:27 UTC
than the filter should be removed.

If you want to have an filter is should not say if you don't activate this I will show you all effects that are not supported. It's way to complicated. A filter ordinary mean if you use the filter you get a subgroup of something.
Comment 3 Martin Flöser 2016-09-04 20:23:54 UTC
I asked for an elaboration for the change. My questions were without any judgment from my side. I just want to have an explanation on why this should be changed. It reads to me like you assumed I'm against the change per se. I don't understand the requested change, so I need more information.
Comment 4 andreas 2016-09-04 20:27:23 UTC
sorry.
Comment 5 Thomas Pfeiffer 2016-09-05 10:41:44 UTC
I would indeed just remove the filter thing. If we don't want users to see something, don't let them see it, why have an option to show it anyway?
Comment 6 Martin Flöser 2016-09-05 10:59:31 UTC
> If we don't want users to see something, don't let them see it, why have an option to show it anyway?

From a KWin maintenance and bug report perspective: we get requests to have the internal effects disabled. Thus we need to make it possible for users to disable them.

Concerning unsupported effects: we need to make it possible to modify the settings when an effect makes the system unusable.
Comment 7 andreas 2017-01-03 00:05:15 UTC
if the filter is needed for "bugtracking" or whatever it should be called, than add some usefull stuff for the filter.