GNOME Bugzilla – Bug 351247
GtkScrolledWindow is mis documented
Last modified: 2010-10-15 18:34:51 UTC
Documentation Section: Gtk+ -> Gtk+ Widgets and Objects -> Scrolling -> GtkScrolledWindow Hello, The documentation say almost nothing about GtkScrolledWindow signals. Correct version: Explanation of move-focus-out and scroll-child signals. Other information: Thanks.
Created attachment 108507 [details] [review] Doc for ::move-focus-out and ::scroll-child for GtkNotebook and GtkScrolledWindow Patch adds the requested documentation. Also documentation for the GtkNotebook::move-focus-out signal because it is roughly equivalent to the GtkScrolledWindow::move-focus-out signal.
Applies cleanly, quick fix. http://live.gnome.org/GtkLove/PatchTriaging spam.
Please have a look at how I've documented keybinding signals in e.g. GtkTextView. I'd like to keep the style relatively uniform, both wrt to the reference to the keybinding section and to the default bindings: * The ::move-cursor signal is a * <link linkend="keybinding-signals">keybinding signal</link> * which gets emitted when the user initiates a cursor movement. * The default bindings for this signal are * Delete for deleting a character, Ctrl-Delete for * deleting a word and Ctrl-Backspace for deleting a word * backwords.
Björn, could you update your patch with mclasen comments?
Björn, Ping :)
Hm. Björn was simply not CCed. Now trying to ping again ;-)
Hm. Björn hasn't responded so far. Shall we reject the patch and close as INCOMPLETE?
Errm, what about pinging the reporter instead of the patch contributor?
Created attachment 172077 [details] [review] Doc for ::move-focus-out and ::scroll-child for GtkScrolledWindow Here a updated patch against current master with mclasen comments.
Review of attachment 172077 [details] [review]: Looks ok
Comment on attachment 172077 [details] [review] Doc for ::move-focus-out and ::scroll-child for GtkScrolledWindow commit cbc358ead8b75522655ddbda3be36d98c8fbebff
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.