ruby-****@sourc*****
ruby-****@sourc*****
2012年 9月 1日 (土) 09:06:43 JST
-------------------------
REMOTE_ADDR = 70.49.49.99
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-txtw-scrolledwin
-------------------------
@@ -22,7 +22,7 @@
One of the decisions you have to make when setting up a scrolled window is to specify when the scrollbars will be visible (Gtk::ScrolledWindow#set_policy(hscrollbar_policy, vscrollbar_policy)). This is done with the policy arguments, which take one of the values defined in ((<GtkPolicyType|Gtk#GtkPolicyType>)). Though unlikely, another thing you may wish to set is the placement of the scrollbars. For that you have Gtk::Scrollbar#window_placement=(window_placement) method at your disposal. Look for the correct argument values at ((<GtkCornerType|Gtk#GtkCornerType>)).
-After you have setup a scrolled window you should add a child widget which you intend to slide around with your scrollbars. There are two possible ways of doing this, and the method is chosen based on the type of child widget. If you are adding to your scrolling window a Gtk::TextView, Gtk::TreeView, Gtk::IconView, or Gtk::Layout widget you should use Gtk::Container#add method, since all five of these containers include native scrolling support.
+After you have setup a scrolled window you should add a child widget which you intend to slide around with your scrollbars. There are two possible ways of doing this, and the method is chosen based on the type of child widget. If you are adding to your scrolling window a Gtk::TextView, Gtk::TreeView, Gtk::IconView, or Gtk::Layout widget you should use Gtk::Container#add method, since all four of these containers include native scrolling support.
All other GTK+ widgets, such as our Gtk::Table, which do not have scrolling support, you must first add to a Gtk::Viewport widget, and then add the Gtk::Viewport to the scrolled window. Though this longer method of adding a widget without the scrolling support to the scrolled window, demonstrates precisely what happens, when you use a convenience method Gtk::ScrolledWindow#add_with_viewport, which does exactly what we have just described. Namely, it adds the scrolling ability to a child widget such as for instance to our table, adds it (the table) to the viewport, and finally adds this viewport with the child (table) to the scrolling window.
@@ -90,7 +90,7 @@
window.show_all
Gtk.main
-The scrolled window is simply a container with scrollbars. Neither the container nor the scrollbars perform any action by themselves. Scrolling is handled by the child widget, which is why the child widget must have a scrolling support. As you know by now, most GTK+ widgets originally do not include such a support - we mentioned only five that do (Gtk::TextView, Gtk::TreeView, Gtk::IconView, or Gtk::Layout). For all these other widgets, without native scrolling support, scrolling behaviour is added with the help of portview.
+The scrolled window is simply a container with scrollbars. Neither the container nor the scrollbars perform any action by themselves. Scrolling is handled by the child widget, which is why the child widget must have a scrolling support. As you know by now, most GTK+ widgets originally do not include such a support - we mentioned only four that do (Gtk::TextView, Gtk::TreeView, Gtk::IconView, or Gtk::Layout). For all these other widgets, without native scrolling support, scrolling behaviour is added with the help of portview.
Adjustments are tightly related to scrolling. When user clicks and drags a scrollbar, the value in adjustment object changes and causes((*value-changed*))signal to be emitted, which subsequently will cause the child to render itself accordingly.