Bug 414745 - Alternative mode for Panel coloring
Summary: Alternative mode for Panel coloring
Status: RESOLVED INTENTIONAL
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.9.4
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-02 11:10 UTC by Mufeed Ali
Modified: 2019-12-02 15:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
This is what i mean (247.76 KB, image/png)
2019-12-02 11:10 UTC, Mufeed Ali
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mufeed Ali 2019-12-02 11:10:33 UTC
Created attachment 124261 [details]
This is what i mean

It would be nice to have an option to give priority to the touching or maximized window instead of the active window when coloring a window that is shown over a maximized window. It would give a more uniform appearance to the UI.
Comment 1 Michail Vourlakos 2019-12-02 13:01:25 UTC
sorry I do not agree. What you are describing was the initial implementation, after I used it for a while it was creating a massive confusion... Colors are too important. In your screenshot if the top bar was colored based on the touching window and not the active then it is pretty easy to confuse the user. The top panel usually contains the window title, appmenu etc... if it is colored differently then this is creating confusion...
Comment 2 Mufeed Ali 2019-12-02 15:00:07 UTC
(In reply to Michail Vourlakos from comment #1)
> sorry I do not agree. What you are describing was the initial
> implementation, after I used it for a while it was creating a massive
> confusion... Colors are too important. In your screenshot if the top bar was
> colored based on the touching window and not the active then it is pretty
> easy to confuse the user. The top panel usually contains the window title,
> appmenu etc... if it is colored differently then this is creating
> confusion...

Ah, i can understand. Is allowing it as a separate option impossible?