xembed test example, gtk-client sending strange message

Andreas Aardal Hanssen xdg at andreas.hanssen.name
Tue Aug 19 11:33:09 EEST 2003

Hi, there.

I'm testing gtk-client.c in the xembed-0.5/tests dir with my xembed 
embedder. My client plugs right in, no problem. But if I try gtk's 
client with my embedder, I see strange results.

Compiled the client with gtk+-2.2.2 using RedHat's 3.2.2 20030222 gcc

gcc -I /home/andreas/opt/gtk+-2.2.2/lib/gtk-2.0/include -I 
/usr/include/atk-1.0 -I/home/andreas/opt/gtk+-2.2.2/include 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include -I 
/home/andreas/opt/gtk+-2.2.2/include/gtk-2.0 gtk-client.c gtk-common.c 
-L /home/andreas/opt/gtk+-2.2.2/lib -lgtk-x11-2.0 -o gtk-client

I start my embedder, then run:

./gtk-client 0x4200007

The first that happens is that gtk-client sends 6 XEMBED messages to my
embedder, whose l[1] field has a value of 108, which doesn't really make
any sense to me.

I also get no ReparentNotify, the event catch to initialize the client. So
my questions to this list are:

1) Why does gtk-client send these messages?
2) Why don't I get a reparentnotify?

Thanks for the help so far,

Andreas :-)

Andreas Aardal Hanssen

More information about the xdg mailing list