gtk-container, gtk-widget, gtk-buildable, g-object, common-lisp:standard-object, common-lisp:t

None

Together with gtk-plug, gtk-socket provides the ability to embed widgets from one process into another process in a fashion that is transparent to the user. One process creates a gtk-socket widget and passes that widget's window ID to the other process, which then creates a gtk-plug with that window ID. Any widgets contained in the gtk-plug then will appear inside the first application's window.

The socket's window ID is obtained by using the function gtk-socket-id. Before using this function, the socket must have been realized, and for hence, have been added to its parent.

Example: Obtaining the window ID of a socket.

GtkWidget *socket = gtk_socket_new ();
gtk_widget_show (socket);
gtk_container_add (GTK_CONTAINER (parent), socket);


/* The following call is only necessary if one of
 * the ancestors of the socket is not yet visible.
 */
gtk_widget_realize (socket);
g_print ("The ID of the sockets window is
          %<GTKDOCLINK HREF="x">x</GTKDOCLINK>n",
         gtk_socket_get_id (socket));  

Note that if you pass the window ID of the socket to another process that will create a plug in the socket, you must make sure that the socket widget is not destroyed until that plug is created. Violating this rule will cause unpredictable consequences, the most likely consequence being that the plug will appear as a separate toplevel window. You can check if the plug has been created by using the gtk-socket-get-plug-window function. If it returns a non-nil value, then the plug has been successfully created inside of the socket.

When GTK is notified that the embedded window has been destroyed, then it will destroy the socket as well. You should always, therefore, be prepared for your sockets to be destroyed at any time when the main event loop is running. To prevent this from happening, you can connect to the "plug-removed" signal.

The communication between a gtk-socket and a gtk-plug follows the XEmbed protocol. This protocol has also been implemented in other toolkits, e.g. Qt, allowing the same level of integration when embedding a Qt widget in GTK or vice versa.

The gtk-plug and gtk-socket widgets are only available when GTK is compiled for the X11 platform and GDK_WINDOWING_X11 is defined. They can only be used on a gdk-x11-display.

The "plug-added" signal

 lambda (socket)    :run-last      

The signal is emitted when a client is successfully added to the socket.

socket

The gtk-socket object which received the signal.

The "plug-removed" signal

 lambda (socket)    :run-last      

The signal is emitted when a client is removed from the socket. The default action is to destroy the gtk-socket widget, so if you want to reuse it you must add a signal handler that returns true.

socket

The gtk-socket object which received the signal.

Returns

True to stop other handlers from being invoked.