Bug 268517 - GUI control for BorderlessMaximizedWindows option
Summary: GUI control for BorderlessMaximizedWindows option
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 21:21 UTC by Nikita Churaev
Modified: 2012-10-02 19:17 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Churaev 2011-03-14 21:21:42 UTC
Version:           unspecified
OS:                Linux

There should be GUI option for this in System Settings.

Reproducible: Always
Comment 1 Thomas Lübking 2011-03-14 21:26:55 UTC
"kcmshell4 kwinoptions" / "Moving" tab -> "Display borders on maximized windows"
Comment 2 Thomas Lübking 2011-03-14 21:30:00 UTC
Sorry, my bad - you're asking for the the netbook thing ;-)

I guess that's a wontfix (netbook settings should just not be broken) - Unless you've another reason to request this.
Comment 3 Weng Xuetian 2011-03-21 17:19:48 UTC
I think even remove that netbook will also work with full function.

I currently at this option to kwinrc and use plasma-desktop. It works quite well. 

Actually I think this option is similar to any other option that changes while switch to netbook, like window placement. If other option can be configured with GUI, there is no reason that this option is an exception.
Comment 4 Thomas Lübking 2011-03-21 18:14:55 UTC
Window placement et al. have been there before netbooks were even invented and are of use on a real desktop.
The fact that the netbook mode (iff) implicitly picks a particular one doesn't matter here at all.

The undecorated maximized setting is however specific for the netbook case and would cause trouble if activated in a general setup (no button to unmaximize or do else on the window - the user will have to know about alt+f3 or use some specific side WM, eg. a plasmoid - which can then set this mode when activated)

Therefore it's rather an implicit setting only and not sth. to be exposed to the curious user - unless you can name a good reason why it is useful in the "normal" window management context (withOUT any sidearm WM on the desktop/panel)
Comment 5 Stefan Majewsky 2011-07-07 07:47:15 UTC
(In reply to comment #4)
> unless you can name a good reason why it is useful in the
> "normal" window management context (withOUT any sidearm WM on the
> desktop/panel)

Saving space is not only relevant on netbooks. Even on my Full HD monitor I want the desktop shell's chrome to be as small and unobstrusive as possible. See:

http://majewsky.wordpress.com/2010/03/24/the-kwin-button-applet/
Comment 6 Thomas Lübking 2011-07-07 12:33:00 UTC
(In reply to comment #5)
> > withOUT any sidearm WM on the desktop/panel

In that the button plasmoid is not different from the netbook shell and can and probably should by default activate the borderless mode.
That is far more natural than telling the user to activate and later on maybe deactivate that setting.

The problems start when clients "forget" to unset the setting or you've multiple clients related to this (you unset it, but there's another item that actually wants it)

=> the problem is (imo) that it's stored as persistent setting. It should rather be a counter on the root window (-> we need a KWindowSystem function for this...)
Perhaps in a bitmask, returning the bit that was set by the client so it can unset that exact bit (as often as it wants to ;-)

high entropy version:
void KWindowSysten::setMaximizedBorderless(bool, int &mask);
Comment 7 Martin Flöser 2012-03-14 15:44:36 UTC
As explained it's an option introduced specificly for the netbook shell. Given that I am against exposing that option in the general user interface.

What I have as an idea on my todo list is to drop the option alltogether and replace it by a KWin script. This would be exposed to the script config module. I do not know whether I will get this done for 4.9 or if it has to wait for 4.10. But given the plans it renders this feature request as not worth to implement.
Comment 8 rockonthemoonfm 2012-10-02 16:59:32 UTC
It could be really useful to add a kwin script to undecorate maximized windows.

It is possible to decorate the windows when unmaximized if you use Current Application Control plasmoid, as found as in the netbook shell.
Probably this esciprt could be automatically activated - and only - when this plasmoid is in use.

I like it, with the menu bar on top you should achieve a Unity shell setup.
Comment 9 Thomas Lübking 2012-10-02 19:17:39 UTC
hah? what?

While I frankly can make only little sense out of the last comment, a plasmoid could offer to alter this setting as well as automatically adjust it
There's absolutely no need to do this by a kwin script (loaded by a plasmoid =) - even a bash one-liner could do the job.

-> file a wish against the plasmoid to take care of this, if the author needs help, he can anytime approach the kwin mailing list