----- Germán Arias <germanan...@gmx.es> a écrit : > On 2014-11-23 12:02:47 -0600 Christophe <christophe.cu...@free.fr> wrote: > > ----- Germán Arias <germanan...@gmx.es> a écrit : > >> [...] > > > > Hi, > > Another thing to look at would be: > > - check the Attributes defined for the window, this can be done by > > accessing > > the window menu with shortcut "Ctrl+Escape" (if not, you can check in > > WPrefs > > -> Keyboard Shortcut -> Open window commands menu), and see if the "Disable > > titlebar" is checked in the attribute dialog). > > Unfortunately this don't work for those windows. After selected Attributes in > menu, the window appears but is closed immediately. With other windows this > works fine.
Strange, should not be the case, but it is probably linked to the thing below? > > If it is checked, it would be interesting for the investigation to know if > > it > > comes from your config (I guess it would be in WMWindowAttributes) or from > > the app; > > The file "WMWindowAttributes" only contains information of icons. This is probably good. > > - run "xprop" and click on the window, and check if the "override redirect" > > is set somewhere; if it is then it is likely that the bug is on the app > > side; > > if not it would be interesting to see the properties defined to check if > > one > > may be the cause of the problem. > > Here the output: > > german@german-desktop:~$ xprop > [...] > _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_MENU This attributes is set from the application to tell that the window is only a menu, and as such window managers should not add stuff (titlebar, resizebar, ...) to it. So I would think that WindowMaker is doing the right thing, probably just a side effect of implementing properly the support of NET_WM attributes (a quick search seems to shows it happened in a 2004 patch). I'd bet on a bug in the toolkit/application, then? Regards, Christophe. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
