Bug#247252: kwin: random buttons missing from titlebar
* Zygo Blaxell at Work [Tue, 04 May 2004 12:23:56 -0400]:
> The behavior seems to be defined more by the toolkit the application
> was written with than whether the buttons in question are useful.
> For example all Tk apps I've tried so far lack the maximize button in
> kwin but get the maximize button in all other window managers that I've
> tried (except of course the WM's that don't have maximize buttons at all).
Does the maximize button actually work? I've tried texdoctk under
sawfish and yes, there was a maximize button, but it didn't work.
That's why I say not displaying some buttons is a good thing, if they
can't be used.
> I've tried several WMs and the only behavior consistent with kwin is that
> gnome-xbill doesn't get a maximize button on either kwin or metacity.
> This makes sense as the gnome-xbill window is not resizeable at all.
And the gnome-xbill app clearly states so. I *think* the applicable
standard is <http://www.freedesktop.org/standards/wm-spec/>:
Fixed size windows
Windows can indicate that they are non-resizable by setting
minheight = maxheight and minwidth = maxwidth in the ICCCM
WM_NORMAL_HINTS property. The Window Manager MAY decorate such
windows differently.
> > In previous versions, kwin always showed
> > all three buttons, but you would find that clicking them would do
> > nothing depending on the app.
> This is incorrect. Clicking the min/max buttons worked as expected
> until kwin 3.2.2.
I don't think clicking the maximize button in gnome-xbill would do a
thing, but hey, maybe I'm misremembering.
> My understanding of the protocol involved is that...
My understanding of the protocol involved is practically null, so I
might be completely wrong. But I'm pretty sure of what I'm saying.
> I think that most of the applications I am having problems with were
> written before the option to not display WM buttons was widely supported
> in window managers, if not before the option was even defined, so I
> don't see how the application could be explicitly requesting anything
> of the sort.
It's a possibility. Really don't know when was this introduced. But
xload seems a pretty old app and it manages not to get minimized ever.
I definitely would appreciate some insight wrt this.
cu
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
When you don't know what to do, walk fast and look worried.
Reply to: