ruby-****@sourc*****
ruby-****@sourc*****
2012年 11月 4日 (日) 04:57:39 JST
-------------------------
REMOTE_ADDR = 184.145.83.139
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-mnstbs-mnui
-------------------------
@@ -110,7 +110,7 @@
:Note:
The distinction between menu items and sub-menus in a narrative can become blurry, graphics clears the confusion by placing a little arrow beside each menu item which is a menu. If you imagine the string '/menu/' in the narrative above represents the arrow the text may also become more clear. You may need to add visual and/or descriptive aids like this to your documents, when you are planning or documenting menus with many sub-menus.
-Menu items in every menu can be either (1) final "leaf" items, which trigger by the developer provided action when user selects such a leaf menu item, or (2) sub-menus for which Gtk default action is to open the menu assigned to the selected (non-leaf) sub-menu item in a cascading fashion, and usually no callback is specified by the developer for these sub-menu items (with the arrow on the side).
+Menu items in every menu can be either (1) final "leaf" items, which trigger by the developer provided action when a user selects such a leaf menu item, or (2) sub-menus for which Gtk default action is to open the menu assigned to the selected (non-leaf) sub-menu item in a cascading fashion, and usually no callback is specified by the developer for these sub-menu items (with the arrow on the side).
In our program example the 'mk_submenu' method can receive more than two arguments. The last argument must be a Boolean value, indicating whether the returned sub-menu should contain a tear-off menu item. All the arguments before the 'tearoff' Boolean argument are either leaf menu items, i.e. strings explicitly defining menu item names, or other sub-menus, which you should have previously created (note that the name of a sub-menu item is now not available, since its place is taken by the menu object).