ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 13日 (木) 06:38:08 JST
-------------------------
REMOTE_ADDR = 184.145.81.223
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -894,7 +894,7 @@
set_dnd_destination_frame_widget(dest_widg, src_widg)
end
- The above call from within the 'set_dnd_destination_frame_widget' method would be recursive if the requirement that each time the 'set_dnd_destination_frame_widget' method is called also the 'drag-drop' signal was emitted. This indeed is not the case, since we have just responded to the initial 'drag-drop' event, and are still in the process of turning the two source and destination frame (widget) associations around, and two consecutive drops one after another are out of the question. No way, any user can not be that quick;)
+ The above call from within the 'set_dnd_destination_frame_widget' method would be recursive if the requirement that each time the 'set_dnd_destination_frame_widget' method is called also the 'drag-drop' signal was emitted. This indeed is not the case, since we have just responded to the initial 'drag-drop' event, and are still in the process of turning the two source and destination frame (widget) associations around, and two consecutive drops one after another are out of the question. No way, any user can be that quick;)
Finally, after you have seen, the temporary nature of source and destination widgets (frames) in either of our 'dnd-toolbar*.rb' programs, you may better understand the reasons we use source and destination widgets as arguments to these instance methods, rather than instance variables.