On Tue, 2011-02-01 at 21:07 +0100, Uli Schlachter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Am 01.02.2011 08:39, Ng Oon-Ee wrote:
> > After some more testing (with other apps as well), it seems the
> > 'offending' hint is this one (from xprop):-
> > 
> > WM_TRANSIENT_FOR(WINDOW): window id # 0x5a00001
> > 
> > How does awesome handle this particular hint/
> 
> I can't find anything in the C core actually using this, except for the 
> stacking
> order (client's are above the window for which they are transient).
> It's available to lua via c.transient_for. The only thing that uses this is
> awful.tag. When a new client with a transient_for hint appears, it gets the 
> same
> screen and tags as its transient for client.
> 
> So, that shouldn't have anything to do with this.
> 
> Cheers,
> Uli

Hmm, just retested, while yesterday I could not find the parent window
today I can. Here's xwininfo -id 0x5600001 (which is the ID currently
under WM_TRANSIENT_FOR for the app.

xwininfo: Window id: 0x5600001 "e-Sword"

  Absolute upper-left X:  640
  Absolute upper-left Y:  400
  Relative upper-left X:  640
  Relative upper-left Y:  400
  Width: 1
  Height: 1
  Depth: 24
  Visual: 0x21
  Visual Class: TrueColor
  Border width: 1
  Class: InputOutput
  Colormap: 0x4800001 (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsUnMapped
  Override Redirect State: no
  Corners:  +640+400  -1917+400  -1917-621  +640-621
  -geometry 1x1+640+400

So it seems there's an unmapped parent window with a 1x1 pixel size. How
would this affect tiling?


-- 
To unsubscribe, send mail to [email protected].

Reply via email to