GTK Socket and reparenting

2013-11-26 Thread Michal Fizek
Hi, i have a problem with GTK Socket. I'm using it to build some GUI for my beloved urxvt terminal emulator. But I encountered a big problem, when i need to split screens. URXVT support xembed, so i use GTK Socket to create window, and pass socked id to urxvt, that plugs and embeds itself into

Re: GTK Socket and reparenting

2013-11-26 Thread Denis Linvinus
i'm not sure that understand you correctly but, try to return true on connect event of the socket. for example var sock = new Gtk.Socket(); sock.plug_removed.connect(()=>{ return true;//important! allow reuse of socket }); 2013/11/26 Michal Fizek > Hi, > i have a problem with GTK Socket

Re: GTK Socket and reparenting

2013-11-26 Thread Michal Fizek
Actually Gtk.Socket is usable, but the window, that is plugged into the socket gets destroyed(like if Gtk.Plug() was plugged into Socket, but after Socket reparenting, Gtk.Plug() is destroyed). I tried what you have suggested of course, but result is the same.

Re: GTK Socket and reparenting

2013-11-26 Thread Bernhard Schuster
Did you try to add an additional reference to your widget? (i.e. explicitly call g_object_ref (your_widget) ) On Tue, Nov 26, 2013 at 3:18 PM, Michal Fizek wrote: Actually Gtk.Socket is usable, but the window, that is plugged into the socket gets destroyed(like if Gtk.Plug() was plugged into

Re: GTK Socket and reparenting

2013-11-26 Thread Michal Fizek
Yes i did. Well actually im using python, but i hold reference to an object(truth is i dont know, if its enough). But probably its the child window(if someone want to bother to try im running: urxvt -embed winid , where winid is my created socketid and urxvt is terminal rxvt-unicode) problem, th