ruby-****@sourc*****
ruby-****@sourc*****
2012年 10月 30日 (火) 08:41:39 JST
-------------------------
REMOTE_ADDR = 74.14.158.59
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-mnstbs-mnui
-------------------------
@@ -38,7 +38,7 @@
{{image_left("mitems-n-submenus.png")}}
-In the next example we expand our program from section [9.1] entitled: ((<Pop-up Menus|tut-gtk2-mnstbs-popup>)). Due to the complexity that is introduced by multi-dimensional menus this example is split into two parts. In the first part we build and implement a realistic menu hierarchy architecture, which you often encounter in real life applications, and in the second we add signal handlers and callbacks. Indeed we continue to use the context menu from from section [9.1]. The difference is that now we added submenus. The menu hierarchy is built with the help of 'mk_submenu' helper method, which serves to build a submenu (note, submenu is an object of Gtk:Menu class). As you can see on the image here on the left, this time we have two levels deep menu hierarchy. 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) submenus for which Gtk default action is to open the menu
assigned to the selected (non-leaf) submenu item in a cascading fashion.
+In the next example we expand our program from section [9.1] entitled: ((<Pop-up Menus|tut-gtk2-mnstbs-popup>)). Due to the complexity that is introduced by multi-dimensional menus this example is split into two parts. In the first part we build and implement a realistic menu hierarchy architecture, which you often encounter in real life applications, and in the second we add signal handlers and callbacks. Indeed we continue to use the context menu from from section [9.1]. The difference is that now we added submenus. The menu hierarchy is built with the help of 'mk_submenu' helper method, which serves to build a submenu (note, submenu is an object of Gtk:Menu class). As you can see on the image here on the left, this time we have two levels deep menu hierarchy. 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) submenus for which Gtk default action is to open the menu
assigned to the selected (non-leaf) submenu item in a cascading fashion, and usually no callback is specified for these submenu items.
{{br}}
{{image_right("submenus-w-tearoff.png")}}