Indicate isBusy backgrounds for Dynamic Background feature
Closed, ResolvedPublic

Description

For Dynamic Background when options
"Hide background for no maximized windows" is enabled
and "Monochrome contents when panel is transparent" is also enabled

enforces transparency in somes cases but there are backgrounds that are too busy in order to provide enough contrast. As elementary approached this : https://medium.com/elementaryos/elementary-os-5-juno-is-here-471dfdedc7b3

the background is considered Busy or not. When the background is busy then is such cases a transparent background is shown

@trmdi is it possible to check this out?
I have uploaded the code to support this, I am not sure this works 100% perfectly but for simple cases it should be ok...

mvourlakos updated the task description. (Show Details)Jan 5 2019, 11:39 AM
trmdi added a comment.Jan 5 2019, 4:12 PM

Ok, I'm testing it. I will report to you if I find something need to be improved. :)

trmdi added a comment.EditedJan 6 2019, 2:04 AM

I think we should have an dropdown in case the monochrome option is enabled. This dropdown has these 3 options:
+ Transparent dark/light (when the Hide background option is enabled)
+ Translucent dark/light (when the Hide background option is disabled)
+ Automatically (default, not depend on the Hide background option, that option will be locked)
This would fit all use cases.

trmdi added a comment.EditedJan 6 2019, 2:29 AM

Because when the user chooses Hide background... That means he never wants a background, vice versa.

trmdi added a comment.EditedJan 6 2019, 4:29 AM

Rename:

+ "Force solid background for maximized or snapped windows" -> Force solid background when touching a window
+ "Hide background for not maximized windows" -> Hide background when not touching any window
+ "Monochrome contents when panel is transparent" -> Monochrome contents when not touching any window

@trmdi I opened https://phabricator.kde.org/T10274 in order to move the Dyn.Background options discussion to a more suitable place.

it is fixed now...

mvourlakos closed this task as Resolved.Mar 18 2019, 12:55 PM