[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #12 from Christoph Feck --- See bug 313244. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #11 from Martin Flöser --- (In reply to Nate Graham from comment #9) > Martin, if the current approach is objectionable, what would you consider to > be an appropriate way for Latte-dock users to gain the functionality in > question? To add this option to the KWin kcm - where it belongs. Then all users could use it and all config is in one place. It's absolutely unacceptable to modify configuration of other applications. Imagine all applications would modify KWin config. Guess what a mess this would create. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #10 from tr...@yandex.com --- (In reply to Martin Flöser from comment #8) > The problem is that we don't know about it and that we get bug reports for > it. It's unacceptable that any application except KWin changes KWin's > configuration. My normal reaction to this is to rename the config key so > that the other software breaks and the devs get the message. I've tried searching for bugs relate to "BorderlessMaximizedWindows". There is only one report. In the same time, there are so many invalid reports here. I don't think that Latte option will lead users file so many bug reports for KWin here. Because that option is disabled by default, users have to enable it, and they would be aware of what they are doing. But it would be better if you have a better approach. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #9 from Nate Graham --- Martin, if the current approach is objectionable, what would you consider to be an appropriate way for Latte-dock users to gain the functionality in question? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #8 from Martin Flöser --- The problem is that we don't know about it and that we get bug reports for it. It's unacceptable that any application except KWin changes KWin's configuration. My normal reaction to this is to rename the config key so that the other software breaks and the devs get the message. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #7 from tr...@yandex.com --- (In reply to Martin Flöser from comment #6) > I hope this is a bad joke that latte dock changes KWin configuration. I don't understand why you always hate that. Latte-dock changes it **only if** the user wants and tells it to do that. What is the problem with it? Latte only helps the users to automate things. If Latte doesn't supply that feature, the user will very likely do it manually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #6 from Martin Flöser --- I hope this is a bad joke that latte dock changes KWin configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 Niklas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Niklas --- Setting this up in Latte-dock fixed this for me. Thanks! Closing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 tr...@yandex.com changed: What|Removed |Added CC||tr...@yandex.com --- Comment #4 from tr...@yandex.com --- If you use Latte-dock, it's a feature: https://github.com/psifidotos/Latte-Dock/wiki/Tips-&-Tricks#q-can-i-have-different-borderlessmaximized-windows-option-between-different-layouts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 --- Comment #3 from Niklas --- David, I honestly can't remember how I originally set it up. Now I do it manually every time I logon, simply by opening ~/.config/kwinrc and changing line: BorderlessMaximizedWindows=false to: BorderlessMaximizedWindows=true -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- >out of by setting BorderlessMaximizedWindows=true Setting how? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 groveover changed: What|Removed |Added CC||a...@gajewiak.com --- Comment #1 from groveover --- The same problem in KDE Neon after update to Plasma 5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396636] BorderlessMaximizedWindows in kwinrc is reset to false at system startup
https://bugs.kde.org/show_bug.cgi?id=396636 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
