❦ 8 septembre 2013 15:06 CEST, Uli Schlachter <[email protected]> :
>> Some programs like to resize and replace themselves after start. This is >> annoying as they may move to another screen. For example, Wireshark is >> like that. >> >> It uses GTK but ultimately, this is the call to XResizeWindow or >> XMoveResizeWindow which triggers this behaviour. Would it be possible to >> tell Awesome to ignore those? >> >> If not, such a behaviour could be overrident with LD_PRELOAD. For >> example, there is already something done specifically for Steam about >> this: >> https://github.com/dscharrer/steamwm >> >> However, I would like something more generic that I could LD_PRELOAD for >> the whole session. Unfortunately, there are some legit use of >> XMoveResizeWindow. Would it be possible for Awesome to help me when to >> prevent such a resize? For example, is it possible for Awesome to set a >> property on a window that I could easily read when intercepting >> XMoveWindow? > > There is no "easy" way to do this in awesome. No idea what you mean with that > property thing, but when a window resizes itself, the X11 server sends a > ConfigureRequest to awesome. This ends up in event.c, > event_handle_configurerequest() where awesome just allows that change. If you > know some C, this is the place were $MAGIC could be done to "defeat" > XMoveResizeWindow(). Oh, I didn't know that the window manager could prevent the move. That's better. Initialy, I was thinking about exposing some properties to help a third party library determine if a window should be allowed to resize or not. If the window manager can prevent the resize (or execute it differently), then I could "just" add a Lua hook at the right place to let the user decide, right? -- Use statement labels that mean something. - The Elements of Programming Style (Kernighan & Plauger) -- To unsubscribe, send mail to [email protected].
