diff --git a/doc/en/Gtk/Widget.xml b/doc/en/Gtk/Widget.xml index d4e8e4938..b8066cbb1 100644 --- a/doc/en/Gtk/Widget.xml +++ b/doc/en/Gtk/Widget.xml @@ -13,7 +13,7 @@ Style properties are set in resource files. This mechanism is used for configuring such things as the location of the scrollbar arrows through the theme, giving theme authors more control over the look of applications without the need to write a theme engine in C. - Use , or to obtain the value of a style property. + Use , or to obtain the value of a style property. diff --git a/doc/en/Gtk/Window.xml b/doc/en/Gtk/Window.xml index a2cb0d2ca..5ef2f01e6 100644 --- a/doc/en/Gtk/Window.xml +++ b/doc/en/Gtk/Window.xml @@ -1,5 +1,5 @@ - + gtk-sharp 0.0.0.0 @@ -7,8 +7,8 @@ Gtk# is thread aware, but not thread safe; See the Gtk# Thread Programming for details. - Toplevel widget that can contain other widgets - Toplevel widget that can contain other widgets + Toplevel widget which can contain other widgets. + Toplevel widget which can contain other widgets. Gtk.Bin @@ -37,9 +37,13 @@ - To be added - an object of type - To be added + Returns a list of all existing toplevel windows. + List of toplevel widgets. + + + The widgets in the list are not individually referenced. If you want to iterate through the list and perform actions involving callbacks that might destroy the widgets, you must call g_list_foreach (result, (GFunc)g_object_ref, ) first, and then unref all the widgets afterwards. + + @@ -55,12 +59,16 @@ - To be added - an object of type - an object of type - an object of type - an object of type - To be added + Starts moving a window. + Mouse button that initiated the drag. + X position where the user clicked to initiate the drag, in root window coordinates. + Y position where the user clicked to initiate the drag. + Timestamp from the click event that initiated the drag. + + + This method is used if an application has window movement grips. When GDK can support it, the window movement will be done using the standard mechanism for the window manager or windowing system. Otherwise, GDK will try to emulate window movement, potentially not all that well, depending on the windowing system. + + @@ -76,12 +84,19 @@ - To be added - an object of type - an object of type - an object of type - an object of type - To be added + Retrieves the dimensions of the frame window for this toplevel. + Location to store the width of the frame at the left, or . + Location to store the height of the frame at the top, or . + Location to store the width of the frame at the returns, or . + Location to store the height of the frame at the bottom, or . + + + It will not return the size of the window border drawn by the window manager, which is the normal case when using a windowing system. See to get the standard window border extents.) See also , . + + + Note: this is a special-purpose function intended for the framebuffer port; see . + + @@ -92,8 +107,15 @@ - To be added - To be added + Asks to iconify (i.e. minimize) the specified . + + + Note that you shouldn't assume the window is definitely iconified afterward, because other entities (e.g. the user or window manager) could deiconify it again, or there may not be a window manager in which case iconification isn't possible, etc. But normally the window will end up iconified. Just do not write code that crashes if not. + + + You can track iconification via the signal on . + + @@ -104,8 +126,15 @@ - To be added - To be added + Asks to unstick window, which means that it will appear on only one of the user's desktops. + + + Note that you shouldn't assume the window is definitely unstuck afterward, because other entities (e.g. the user or window manager) could stick it again. But normally the window will end up stuck. Just do not write code that crashes if not. + + + You can track stickiness via the signal on . + + @@ -116,8 +145,15 @@ - To be added - To be added + Asks to unmaximize . + + + Note that you shouldn't assume the window is definitely unmaximized afterward, because other entities (e.g. the user or window manager) could maximize it again, and not all window managers honor requests to unmaximize. But normally the window will end up unmaximized. Just don't write code that crashes if not. + + + You can track maximization via the signal on . + + @@ -131,10 +167,17 @@ - To be added - an object of type - an object of type - To be added + Obtains the current size of . + Return location for width, or . + Return location for height, or . + + + If window is not onscreen, it returns the size GTK+ will suggest to the window manager for the initial window size (but this is not reliably the same as the size the window manager will actually select). The size obtained by is the last size received in a GdkEventConfigure, that is, GTK+ uses its locally-stored size, rather than querying the X server for the size. As a result, if you call then immediately call , the size would not have taken effect yet. After the window manager processes the resize request, GTK+ receives notification that the size has changed via a configure event, and the size of the window gets updated. + + + Note 1: Nearly any use of this function creates a race condition, because the size of the window may change between the time that you get the size and the time that you perform some action assuming that size is the current size. To avoid race conditions, connect to on the window and adjust your size-dependent state to match the size delivered in the GdkEventConfigure. + + @@ -148,10 +191,14 @@ - To be added - an object of type - an object of type - To be added + Gets the default size of the window. + Location to store the default width, or . + Location to store the default height, or . + + + A value of -1 for the width or height indicates that a default size has not been explicitly set for that dimension, so the "natural" size of the window will be used. + +