https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #10 from leftcrane ---
Yeah, I've looked into this and it seems like this is native behavior for X11.
So there is no way to set the origin elsewhere? It always has to the be in the
left corner?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #8 from leftcrane ---
(actually no that won't work with window snapping. so you'd have to make sure
the primary is always leftmost horizontally, regardless of how the monitors are
actually positioned on your desk).
--
You are
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #7 from leftcrane ---
Either that, or just change the setup to make sure the primary monitor is
always in a specific position in the grid. So if you have three monitors
horizontally, you'd actually have to arrange them vertically wit
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #6 from leftcrane ---
Sorry to nag, but why can't the origin be located on the primary monitor?
Right now I have to move all the windows back to the primary monitor manually
after I connect a secondary, because most of them shift. T
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #3 from leftcrane ---
Is it different in Wayland, btw? If you connect a secondary monitor, will your
coordinates also shift and cause windows to move to the left?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #2 from leftcrane ---
Is there something in X11 that necessitates this? Why can't the origin be
located on the primary monitor (instead of whichever monitor happens to be on
the left)?
I don't agree that nothing is wrong. Nobody
https://bugs.kde.org/show_bug.cgi?id=405807
Bug ID: 405807
Summary: Affix the origin to the primary monitor on X11
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: no
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #31 from leftcrane ---
Thanks for all the work! The bug is indeed fixed.
I also got it working alongside a KWin rule to force all windows to the primary
display. I had to make sure to negate lattedock in the rule, because otherwise
it will
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #26 from leftcrane ---
Created attachment 118957
--> https://bugs.kde.org/attachment.cgi?id=118957&action=edit
latte debug 2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #25 from leftcrane ---
Unfortunately, the issue persists.
1. [ScreenConnectors]
10=DP-1
11=DP-2
12=eDP-1
13=HDMI-1
2. just uploaded.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405639
--- Comment #2 from leftcrane ---
some of them wont even close when you act on them - like chromium notifications
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #23 from leftcrane ---
Created attachment 118952
--> https://bugs.kde.org/attachment.cgi?id=118952&action=edit
latter dock conf
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #22 from leftcrane ---
No, I should have two. I have two panels on DP-2, both assigned to DP-2.
Instead I get four (until I restart latte dock, then I get the correct number,
which is 2)
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #20 from leftcrane ---
Created attachment 118943
--> https://bugs.kde.org/attachment.cgi?id=118943&action=edit
latter debug output.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #19 from leftcrane ---
1. I've tried both - it doesn't matter.
2. See last attachment.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #17 from leftcrane ---
tab-1 is the first half of the settings, tab-2 is the second half (I had to
scroll to capture the entire tab)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #16 from leftcrane ---
ok here it is.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #15 from leftcrane ---
Created attachment 118942
--> https://bugs.kde.org/attachment.cgi?id=118942&action=edit
behavior-tab-2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #14 from leftcrane ---
Created attachment 118941
--> https://bugs.kde.org/attachment.cgi?id=118941&action=edit
behavior-tab-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #13 from leftcrane ---
The tiling behavior is just a symptom/consequence of the panels shifting to the
wrong monitor. The latter behavior is the actual bug.
What's the "behavior tab"?
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #11 from leftcrane ---
correct. They are assigned to DP-2, but when DP-2 is disconnected, they shift
to the primary output. Also tiling is bugged, as you can see in the video.
To fix the problem, I press a hotkey to restart both Kwin and
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #9 from leftcrane ---
Created attachment 118939
--> https://bugs.kde.org/attachment.cgi?id=118939&action=edit
another screenshot
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #8 from leftcrane ---
1. No, I've already checked that. I tried it with plasma panels and the panels
stay on their monitor.
2. Yes. I am not sure why, but it just sometimes shifts a little to the left,
creating a gap. But this behavi
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #6 from leftcrane ---
1. see below.
2. No.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #5 from leftcrane ---
GS_LIB=/home/username/.fonts
KDE_FULL_SESSION=true
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex
https://bugs.kde.org/show_bug.cgi?id=405687
--- Comment #4 from leftcrane ---
Created attachment 118937
--> https://bugs.kde.org/attachment.cgi?id=118937&action=edit
video illustration
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405688
Bug ID: 405688
Summary: Option to move all windows to primary monitor on
display change
Product: kwin
Version: 5.15.2
Platform: Kubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=405687
Bug ID: 405687
Summary: latte panels go haywire with display on the left
Product: latte-dock
Version: git (master)
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #21 from leftcrane ---
re HVM, you can make a big translucent icon overlay right on top of the
windows. It won't actually obscure the content at all. When I was on gnome, I
relied on this extension to make the overview usable for more
https://bugs.kde.org/show_bug.cgi?id=405641
--- Comment #1 from leftcrane ---
Gnome pretty much has this too cause you can bind a key to Settings/Shortcuts
and pull up what is essentially a searchable cheat sheet. KDE unfortunately
doesn't have anything like this.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405641
Bug ID: 405641
Summary: Search system shortcuts from Krunner.
Product: krunner
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=405641
leftcrane changed:
What|Removed |Added
Version|unspecified |5.15.2
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=405640
Bug ID: 405640
Summary: Provide a way to search all shortcuts together.
Product: systemsettings
Version: 5.14.4
Platform: Other
OS: Linux
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=405639
--- Comment #1 from leftcrane ---
"I think it may even be a good idea to make sure that clicking on the body of
the notification behave the same way as this proposed shortcut"
This would be especially relevant for new users who aren'
https://bugs.kde.org/show_bug.cgi?id=405639
Bug ID: 405639
Summary: Make it easier to close or invoke default action on
notification popups
Product: plasmashell
Version: 5.15.2
Platform: Kubuntu Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #9 from leftcrane ---
Oh yeah, no problem. I was just trying to say what I think about a peripheral
aspect of KDE, which I think is pretty bad. I would never use that language to
describe anything that lies at the core of the desktop
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #7 from leftcrane ---
(In reply to Nate Graham from comment #5)
> Are you using an Icons-Only Task Manager or Latte Dock? Or something else?
> And are you using the Breeze Plasma theme (not color scheme), or another
> theme?
This
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #6 from leftcrane ---
Note that Dash to Panel offers tons of options - we don't need most of them.
For example the option to have the running indicator lines on the outer edge of
the dock isn't needed. (see attachment in precedi
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #4 from leftcrane ---
Created attachment 118898
--> https://bugs.kde.org/attachment.cgi?id=118898&action=edit
gnome-indicators-useless-option
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #3 from leftcrane ---
Running apps are actually indicated, confusingly and totally against
convention, using grey highlight boxes. The grey highlight box should identify
the active group only in my opinion. The underline should be used to
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #18 from leftcrane ---
Yes, Gnome is the same. I'd add that identifying windows is hard enough even at
full brightness.
The best solution I've found is to use big, centered icon overlays, like here:
https://extensions.gnome.org
https://bugs.kde.org/show_bug.cgi?id=405380
--- Comment #3 from leftcrane ---
It's finally working with the latest update, but it just takes about 30 seconds
to load all the updates.
If there is no way to make this faster (apt is lighting-fast), I'd recommend
having some progress
https://bugs.kde.org/show_bug.cgi?id=405343
--- Comment #5 from leftcrane ---
OK, makes sense to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405602
--- Comment #1 from leftcrane ---
Created attachment 118884
--> https://bugs.kde.org/attachment.cgi?id=118884&action=edit
generic-themed-indicators
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405602
Bug ID: 405602
Summary: Make the indicator style more legible and
conventional.
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=405600
leftcrane changed:
What|Removed |Added
Platform|Other |Kubuntu Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=405600
Bug ID: 405600
Summary: Click to cycle grouped windows (window switching)
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=405343
--- Comment #3 from leftcrane ---
How about editable type-ahead? This is the standard for GTK file managers.
I really do prefer Nautilus's behaviour, but I doubt it's not going to happen
cause that would be a huge technical challenge, one
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #16 from leftcrane ---
Option 2, no question. Any amount of dimming is going to negatively impact the
visual perception, which is vital when you're looking at small thumbnails. Not
only that, but dimming provides vastly inferior feedba
https://bugs.kde.org/show_bug.cgi?id=405428
--- Comment #3 from leftcrane ---
OK, KWin is feature frozen, so the workaround for this issue becomes:
- Ship a KWin script to move all windows to primary monitor. Maybe have this
script (optionally) fire when a secondary monitor is reconnected
https://bugs.kde.org/show_bug.cgi?id=405428
--- Comment #2 from leftcrane ---
I mean secondary monitor positioned to the LEFT (not the right)
Anyway, I discovered this was intended behavior.
https://www.reddit.com/r/kde/comments/6yeru6/connect_2nd_monitor_kwin_moves_all_open_windows/
I really
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #15 from leftcrane ---
I know, but this isn't about the indicators - it's about the hover effect.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405428
--- Comment #1 from leftcrane ---
I'll just add that some apps appear confused about the primary monitor while
others (like inkscape opening a file) actively want to appear on the right-hand
secondary monitor. (for these latter apps, I have a KWin
https://bugs.kde.org/show_bug.cgi?id=405428
Bug ID: 405428
Summary: Secondary monitor positioned to right acts as a
primary monitor (windows positions are not remembered
either)
Product: kwin
Version: 5.14.3
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #13 from leftcrane ---
lol
it's cause I need the cycle effect. The KDE dock has no decent alternative for
switching between grouped windows. Also the indicators are really poorly
executed.
Imo, Latte dock would be ideal if it kep
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #11 from leftcrane ---
Well, I don't know about you but I am constantly clicking on the wrong items in
the dock precisely because there is no visual feedback to tell me what I am
about to click on.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=405380
Bug ID: 405380
Summary: Apt Updates fail to load in Discover
Product: Discover
Version: 5.15.2
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: no
https://bugs.kde.org/show_bug.cgi?id=405343
--- Comment #1 from leftcrane ---
Basically you start typing and it searches/filters the current directory, with
the first result highlighted. Then you can just press enter and open the
result.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=405343
Bug ID: 405343
Summary: Typing invokes filter function (like Gnome Nautilus)
Product: dolphin
Version: 18.04.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #9 from leftcrane ---
You don't agree with making this an option?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #7 from leftcrane ---
The hovering would be from the plasma theme, just like for the default tasks
widget.
Do you still need more info?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #6 from leftcrane ---
Created attachment 118675
--> https://bugs.kde.org/attachment.cgi?id=118675&action=edit
illustration of the usability problem, even with the parabolic effect.
It's also for global menu, and for all the
https://bugs.kde.org/show_bug.cgi?id=405252
--- Comment #4 from leftcrane ---
Just do it the way plasma already does it. Observe the hover effect "icon only"
task manager that ships with Plasma. (the colors and shapes depend on the theme
being used).
This hover effect is standard
https://bugs.kde.org/show_bug.cgi?id=405252
Bug ID: 405252
Summary: Add a more definite hover effect to improve visual
feedback /accessibility. (normal hover effect, like
you see in menubars etc.)
Product: latte-dock
https://bugs.kde.org/show_bug.cgi?id=404540
Bug ID: 404540
Summary: For Latte dock, option to have alternative indicator
style copied from Gnome's Dash to Panel.
Product: latte-dock
Version: git (master)
Platform: Kubuntu P
https://bugs.kde.org/show_bug.cgi?id=404539
Bug ID: 404539
Summary: Option to require pressure to show the panel.
Product: latte-dock
Version: git (master)
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #11 from leftcrane ---
https://github.com/hughsie/PackageKit/issues/302
PPA's and COPR are supported, but if they misbehave in any way PK updates will
stop working entirely. So they are poorly supported and users should be given
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #9 from leftcrane ---
OK, turned out this was because the cosmic release was removed from the ppa I
was using. (https://launchpad.net/~mdeguzis/+archive/ubuntu/libregeek)
If _any_ repository is down, packagekit can't refresh the
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #8 from leftcrane ---
Output of "pkcon refresh force"
Refreshing cache [=]
Loading cache [=]
Refreshing sof
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #7 from leftcrane ---
Created attachment 117068
--> https://bugs.kde.org/attachment.cgi?id=117068&action=edit
Gnome software example error (one of many)
I've just loaded an example from Gnome Software. It says "failed to
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #6 from leftcrane ---
It's not actually that particular line. Something must have jolted it back into
working order after the apt-update, but now packagekit is back on its bullshit.
I wish I could help more, but this is all I see i
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #3 from leftcrane ---
Turned out that it was just this one repository. However, Discover was giving
me error messages with at least four apt lines.
Unfortunately, I couldn't read or save those messages cause they appeared for
onl
https://bugs.kde.org/show_bug.cgi?id=402306
--- Comment #2 from leftcrane ---
Try with this repository.
# deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ cosmic main
For some reason, third-party repositories cause this problem. It's the same on
Fedora, you have to tick
https://bugs.kde.org/show_bug.cgi?id=402306
leftcrane changed:
What|Removed |Added
Version|unspecified |5.14.4
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=402306
Bug ID: 402306
Summary: PackageKit crashes every time while fetching updates
for Discover
Product: Discover
Version: unspecified
Platform: Kubuntu Packages
OS: Lin
https://bugs.kde.org/show_bug.cgi?id=402209
Bug ID: 402209
Summary: Blank menus on Sublime Text (similar behavior as with
LibreOffice
Product: kded-appmenu
Version: 5.14.3
Platform: Kubuntu Packages
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #18 from leftcrane ---
you mean DWD? stuff like titlebar coloring doesn't require toolkit support or
DWD. it just seemed like it would be relevant to the overall goal of closer
integration between the ssd and apps, which seems worth
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #16 from leftcrane ---
Oh yeah, I forgot all the dark theme apps. So it's actually way more than ten
apps (I have a rule for those though).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #15 from leftcrane ---
Oh these apps don't follow any system color scheme (different toolkit, or it's
a text editor or terminal).
And there is mismatch built into some gtk and kvantum themes, that shows up
under certain cir
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #13 from leftcrane ---
Yeah, I see the problem with video players, for example. But these would be
these exception.
Currently, I have non-matching titlebar/chrome for about 10 apps on my system.
To get them to match, I'd have to pe
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #11 from leftcrane ---
"Capture the inactive and active window chrome"
Capture the color of the chrome, i mean.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #10 from leftcrane ---
a) Having KWin do all the work would of course be ideal (the user would still
be able to override just like they do now with rules). Capture the inactive and
active window chrome at every launch, or capture once at
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #8 from leftcrane ---
The point is inherit some values regarding contrast from the main theme. That
way the user can define as few colors as possible (usually they just need to
define one color).
- contrast between the active titlebar
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #6 from leftcrane ---
TL;DR. The user should be able to change the titlebar color (to match window
chrome or for other reasons) without having to create a whole new color scheme.
Most of the time, all you really need is just the active
https://bugs.kde.org/show_bug.cgi?id=401576
leftcrane changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=402034
leftcrane changed:
What|Removed |Added
Flags|Usability+ |Usability-
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=402034
--- Comment #1 from leftcrane ---
example:
https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402034
Bug ID: 402034
Summary: Provide an easy way to restart KWin and Plasma shell
to the user (from virtual console)
Product: kde-cli-tools
Version: 5.14.4
Platform: Kubuntu Packages
https://bugs.kde.org/show_bug.cgi?id=402030
Bug ID: 402030
Summary: Cycle tabs in most according to last used order in
chromium (like alt tab for kwin)
Product: plasma-browser-integration
Version: unspecified
Platform: Kubu
https://bugs.kde.org/show_bug.cgi?id=401998
--- Comment #3 from leftcrane ---
However I wasn't getting duplicates for other types of notifications, for
whatever reason.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401998
--- Comment #2 from leftcrane ---
I had one notification widget on my desktop and one in the system tray. So they
were both sending the same notification.
Feel free to close this.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=401998
Bug ID: 401998
Summary: Download notification showing up twice
Product: plasma-browser-integration
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: REPORT
https://bugs.kde.org/show_bug.cgi?id=401991
Bug ID: 401991
Summary: Option to make status overlays non-clickable, or hide
them all together (interferes with the primary
function of the dock)
Product: latte-dock
Ve
https://bugs.kde.org/show_bug.cgi?id=400690
--- Comment #7 from leftcrane ---
PS: keeping the minimization states would be "nice" but it's not essential.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400690
--- Comment #6 from leftcrane ---
(In reply to Michail Vourlakos from comment #5)
> (In reply to leftcrane from comment #4)
> >
>
> have you used the mouse wheel behavior for cycling grouped tasks that Latte
> already provides?
https://bugs.kde.org/show_bug.cgi?id=400690
--- Comment #4 from leftcrane ---
i mean the cycle shouldn't permanently affect the minimization state, because
the user just wants to see the windows, not minimize or restore.
So if you have a group of three windows:
* window 1 active,
* win
https://bugs.kde.org/show_bug.cgi?id=400690
--- Comment #2 from leftcrane ---
If you implement this, please don't add minimization to the cycle. I should
just cycle between windows in the group not minimize/restore states.
I know current behavior allows for minimizing by left click on the
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #3 from leftcrane ---
I personally would prefer the titlebar to look different from the chrome, but
with the same base color. Sort of like Adwaita does it. There is trend to have
matching colors: android, Gnome, Mac, Windows, they all do it
https://bugs.kde.org/show_bug.cgi?id=401576
--- Comment #1 from leftcrane ---
Separating the app-specific titlebar color from the color schemes may also make
it possible to specify the titlebar color at launch, which means app-developers
could theoretically define the color value in their
https://bugs.kde.org/show_bug.cgi?id=401576
Bug ID: 401576
Summary: kwin rules for app-specific color themes: facilitate
color matching between titlebar and app color
Product: systemsettings
Version: 5.14.4
Platform: Kubunt
201 - 300 of 331 matches
Mail list logo
