ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 8日 (土) 05:40:15 JST
-------------------------
REMOTE_ADDR = 184.145.89.109
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -339,7 +339,8 @@
Do not pay too much attention to the above 'HikiDBG' auxiliary module. It provides rather useful drag-and-drop debugging methods, which if commented out of the example programs that use them should in no way effect user's experience, unless of course that user is a developer, that would like to observe some of the behind the scene run-time program characteristics. The only thing you should pay attention to is how we are including such auxiliary modules into our programs and developing environment.
-Our 'button-to-label-dnd.rb' example program consists of a single 'DnDWindow' class which is the subclass of the 'BasicWindow' class, i.e. the class defined in the module 'HikiGTK'.
+Our 'button-to-label-dnd.rb' example program consists of a single 'DnDWindow' class which is the subclass of the 'BasicWindow' base class, i.e. the class defined in the module 'HikiGTK'. The BasicWindow base class is a Gtk::Window class, implementing the most rudimentary Gtk::Window behaviour, that any application should always implement. It sets up the top level 'delete_event' and 'destroy' widget signals, sets up the window title if, it is passed to its window constructor, and takes care of the window size and its border. Indeed, you can override all these properties in your main (driving) window subclass.
+
{{br}}