-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea: secondary auto detect #141
Comments
👍 |
I have 4.1.2. And it doesn't seem like anyone's going to make an updated kernel for Haier w910. |
Does this offer any advantages over manually setting the color (you could use the notification color picker so you don't have to take a screenshot yourself)? It looks like something that could noticeably impact performance for little to no convenience. |
No, not constantly. Only once per activity! |
That doesn't answer my question. In fact, it only reinforces my point. |
The advantage is that this would work automatically, just like the current implementation, but in many cases more accurate. |
From my previous comment:
This could basically be the very last resort if we can't get material design apps (#129) to work correctly otherwise, but we'd like to avoid such an approach if possible.
From my previous commentL
|
I'm pretty certain you could detect the colour of a pixel in the top of the foreground app, and use that as the auto detected colour, when your other methods (or if no manual colours are set) don't work. Of course, make that optional
The text was updated successfully, but these errors were encountered: