[ruby-gnome2-doc-cvs] [Ruby-GNOME2 Project Website] update - tut-gtk2-mnstbs-mnui

Zurück zum Archiv-Index

ruby-****@sourc***** ruby-****@sourc*****
2012年 11月 5日 (月) 08:42:44 JST


-------------------------
REMOTE_ADDR = 184.145.95.170
REMOTE_HOST = 
        URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-mnstbs-mnui
-------------------------
@@ -313,7 +313,7 @@
 
     Once we are sure our menu design is correct, we can proceed to step #4 - creating the callback procedures.
 
-    -4-{{br}} According to the way our menu item callbacks will be implemented, which we anticipated already above in section 9.4.1.2 entitled '((<Signal Handling Mechanisms And Callbacks With Sub-menus|tut-gtk2-mnstbs-mnui#Signal Handling Mechanisms And Callbacks With Sub-menus>))', and because our menu design requires that the callback procedures we create are some kind of proc objects, we decided to use lambdas for these callbacks. We can the store these lambdas as Proc objects in the variables, identified above in step #3.a under the column Callbacks.
+    -4-{{br}} According to the way our menu item callbacks will be implemented, which we anticipated already above in section 9.4.1.2 entitled '((<Signal Handling Mechanisms And Callbacks With Sub-menus|tut-gtk2-mnstbs-mnui#Signal Handling Mechanisms And Callbacks With Sub-menus>))', and because our menu design requires that the callback procedures we create are some kind of proc objects, we decided to use lambdas for these callbacks. We can then store these lambdas as Proc objects in the variables, identified above in step #3.a under the column Callbacks.
     
     Since these procedures will are needed in our previous steps, we are required to place them high enough in our program listing, to be visible at the time they are used. To be on the safe side we will place the code creating these procs just before our step #1 above. Following is the code segment presenting the entire step #4 in our program example:
 




ruby-gnome2-cvs メーリングリストの案内
Zurück zum Archiv-Index