On Tue, 05 Jun 2012 10:24:13 +0700 quanta <[email protected]> wrote:
> On 06/04/2012 11:12 PM, Bryan Gardiner wrote: > > > > Since awful.rules.rules are processed in order, maybe something > > lower down in the list is matching and setting it to be > > non-maximized. > No, there is nothing override this: > > [snip] > > I've changed the WM_CLASS to the lowercase and now sometime it get > maximized, sometime it doen't. Okay, I did a bit of poking around in the Terminator source, and the --maximized flag looks like it's failing because Terminator tells its Gtk window to maximize before it's visible. Adding an explicit show() call before maximize() makes the flag work fine. According to the PyGTK docs, maximizing before calling show should work as intended, but with the caveat that maximize() never promises to maximize the window: http://www.pygtk.org/docs/pygtk/class-gtkwindow.html#method-gtkwindow--maximize I wonder, does awesome just drop these maximize() calls because it hasn't layed out the window yet? Cheers, Bryan -- To unsubscribe, send mail to [email protected].
