--- Begin Message ---
Subject: |
24.0.50; X toolkit and parent id |
Date: |
Sat, 03 Apr 2010 18:27:07 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
There is the annoying problem with some WMs, when client sets parent
windows id (PID XID) as NULL (0). You can see with wmctrl -lp, that GTK
toolkit sets PID, and
athena, or something older - not.
I try to search by myself, how to set up PID in lucid toolkit, but don't
have any success.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#5828: 24.0.50; X toolkit and parent id |
Date: |
Sun, 04 Apr 2010 12:54:22 +0200 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 |
I have checked in a fix in trunk.
Jan D.
[AvataR] skrev 2010-04-04 11.00:
There is the annoying problem with some WMs, when client sets parent
windows id (PID XID) as NULL (0). You can see with wmctrl -lp, that GTK
toolkit sets PID, and
athena, or something older - not.
I try to search by myself, how to set up PID in lucid toolkit, but don't
have any success.
What is the problem? _NET_WM_PID is not required and WMs must get by even
if it is not set.
Jan D.
This is not really big problem, but some WMs like matchbox/hildon
filter such windows. This behaviour can be fixed in WM, but I think
will be better if toolkit just set _NET_WM_PID
--- End Message ---