Hi Gang, I am sending X messages to TestGtkEmbed (my own version which sets up a callback on "client_event" signal) to control it through another process. I have had great success sending X events for doing back, load url, etc. I recently extended my partner process to watch for new browser windows being created and it responds just as I had hoped to both javascript creating windows and choosing to create a new browser through the file menu. It reparents the X windows and works great. However, when I send an X event to create a new window I kill the browser. Some things I tried: - I had the file menu open new browser call my new browser code and it works just fine. - I had each different way of spawning a browser print its thread id to make sure that control was being done by the same thread. - I spawned the event from the lowest level on the partner process side so that on the partner side it would respond exactly like an asychronously spawned browser window. I am curious about some comments I have seen in gtkmozembed.cpp::NewBrowser() about looping and waiting for a window to be ready (with no looping actually going on?). Can anyone tell me what I am missing? It seems that I am nearly exactly emulating what takes place when a new browser is created through the file menu. The only difference being the menu spawned variety is taking place on an "activate" signal and the X Send event is happening on "client_event". Thanks for you time, Ron Groth
