ruby-****@sourc*****
ruby-****@sourc*****
2012年 11月 6日 (火) 11:17:58 JST
-------------------------
REMOTE_ADDR = 184.145.95.170
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-mnstbs-mnub
-------------------------
@@ -191,5 +191,4 @@
Though we have already discussed keyboard accelerators in section 9.2 '((<Keyboard Accelerators|tut-gtk2-mnstbs-popup#Keyboard Accelerators>))' now that we are familiar with menus, menu bars, and sub-menus we can expose also the relationships between them and other widgets such as top windows and other nested widgets particularly menu an sub-menu items.
-
-Unfortunately building accelerator path with Gtk::AccelMap.add_entry does not add anything new to the menu designs. Creating 'accel-path' and adding it to the Gtk::AccelGroup seems redundant and incompletely implemented in Gtk. In particular mi.accel_path = "my-acc-p/xyz" has no effect, and fails to display the accelerator key on the menu item! The only thing that works is that callback is is called when accelerator key is pressed. For full treatment of accelerator path see 9.2.1 '((<Accelerator Path|tut-gtk2-mnstbs-popup#Accelerator Path>))'
+Unfortunately building accelerator path with Gtk::AccelMap.add_entry does not bring anything valuable to the menu designs. Creating 'accel-path' and adding it to the Gtk::AccelGroup seems redundant and incompletely implemented in Gtk. In particular mi.accel_path = "my-acc-p/xyz" has no effect, and fails to display the accelerator key on the menu item! The only thing that works is that callback is is called when accelerator key is pressed. For full treatment of accelerator path see 9.2.1 '((<Accelerator Path|tut-gtk2-mnstbs-popup#Accelerator Path>))'