ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 12日 (水) 13:35:29 JST
-------------------------
REMOTE_ADDR = 184.145.81.223
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -841,7 +841,7 @@
The 'set_dnd_source_frame_widget(htbframe)' method is straight forward, nevertheless it contains a few perks that deserve special attention.
- We first register our source widget (frame) as a listener or the signal handler for 'button-press-event' signals (remember the frames normally do not respond to signals), so we first have to add (register) event/signal for our toolbar frame, and then register this frame's callback proc (or block) to respond to emissions of the 'button-press-event' signals. When and if the 'button-press-event' occurs while cursor is hovering over the frame, we make this signal handler to finally register the widget as the dnd source. The perk is that we can not use the regular Gtk::Drag.source_set method to set up our source widget (frame), as we did in our 'button-to-label-dnd.rb' example.
+ In this method we register our source widget (frame) as a listener or the signal handler for 'button-press-event' signals (remember the frames normally do not respond to signals), so we first have to add (register) event/signal for our toolbar frame, and then register this frame's callback proc (or block) to respond to emissions of the 'button-press-event' signals. When and if the 'button-press-event' occurs while cursor is hovering over the frame, we make this signal handler to finally register the widget as the dnd source. The perk is that we can not use the regular Gtk::Drag.source_set method to set up our source widget (frame), as we did in our 'button-to-label-dnd.rb' example.
widg.signal_connect('button-press-event') do |w, e|