GNU bug report logs - #5828
24.0.50; X toolkit and parent id

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 5828 in the body.
You can then email your comments to 5828 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: public.avatar <at> gmail.com ([AvataR])
To: bug-gnu-emacs <at> gnu.org
Subject: 24.0.50; X toolkit and parent id
Date: Sat, 03 Apr 2010 18:27:07 +0300

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.

Message #8 received at 5828 <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: "[AvataR]" <public.avatar <at> gmail.com>
Cc: 5828 <at> debbugs.gnu.org
Subject: Re: bug#5828: 24.0.50; X toolkit and parent id
Date: Sun, 04 Apr 2010 10:16:33 +0200

[AvataR] skrev 2010-04-03 17.27:
> 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.

Message #13 received at 5828-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: "[AvataR]" <public.avatar <at> gmail.com>
Cc: 5828-done <at> debbugs.gnu.org
Subject: Re: bug#5828: 24.0.50; X toolkit and parent id
Date: Sun, 04 Apr 2010 12:54:22 +0200

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

Message #16 received at 5828 <at> debbugs.gnu.org (full text, mbox):

From: public.avatar <at> gmail.com ([AvataR])
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: 5828 <at> debbugs.gnu.org
Subject: Re: bug#5828: 24.0.50; X toolkit and parent id
Date: Sun, 04 Apr 2010 12:00:40 +0300

> > 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.