Synopsis#include <gtk/gtk.h> GtkSocket; GtkWidget* gtk_socket_new (void); void gtk_socket_steal (GtkSocket *socket_, GdkNativeWindow wid); void gtk_socket_add_id (GtkSocket *socket_, GdkNativeWindow window_id); GdkNativeWindow gtk_socket_get_id (GtkSocket *socket_); GdkWindow* gtk_socket_get_plug_window (GtkSocket *socket_); Object HierarchyGObject +----GInitiallyUnowned +----GtkObject +----GtkWidget +----GtkContainer +----GtkSocket DescriptionTogether with GtkPlug, GtkSocket 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 GtkSocket widget and, passes the that widget's window ID to the other process, which then creates a GtkPlug with that window ID. Any widgets contained in the GtkPlug then will appear inside the first applications window.
The socket's window ID is obtained by using
Example 51. 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 %x\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 examining the
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 GtkSocket and a GtkPlug 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.
A socket can also be used to swallow arbitrary
pre-existing top-level windows using DetailsGtkSockettypedef struct _GtkSocket GtkSocket;
The GtkSocket structure contains the gtk_socket_new ()GtkWidget* gtk_socket_new (void); Create a new empty GtkSocket.
gtk_socket_steal ()void gtk_socket_steal (GtkSocket *socket_, GdkNativeWindow wid); Warning
Reparents a pre-existing toplevel window into a GtkSocket. This is meant to embed clients that do not know about embedding into a GtkSocket, however doing so is inherently unreliable, and using this function is not recommended. The GtkSocket must have already be added into a toplevel window before you can make this call.
gtk_socket_add_id ()void gtk_socket_add_id (GtkSocket *socket_, GdkNativeWindow window_id); Adds an XEMBED client, such as a GtkPlug, to the GtkSocket. The client may be in the same process or in a different process.
To embed a GtkPlug in a GtkSocket, you can either create the
GtkPlug with The GtkSocket must have already be added into a toplevel window before you can make this call.
gtk_socket_get_id ()GdkNativeWindow gtk_socket_get_id (GtkSocket *socket_);
Gets the window ID of a GtkSocket widget, which can then
be used to create a client embedded inside the socket, for
instance with The GtkSocket must have already be added into a toplevel window before you can make this call.
Signal DetailsThe
|
|
the object which received the signal |
|
user data set when the signal handler was connected. |
"plug-removed"
signalgboolean user_function (GtkSocket *socket_, gpointer user_data) : Run Last
This signal is emitted when a client is removed from the socket.
The default action is to destroy the GtkSocket widget, so if you
want to reuse it you must add a signal handler that returns TRUE
.
|
the object which received the signal |
|
user data set when the signal handler was connected. |
Returns : |
TRUE to stop other handlers from being invoked.
|