ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 7日 (金) 23:55:45 JST
-------------------------
REMOTE_ADDR = 184.145.84.49
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -138,16 +138,17 @@
:DnD related signals
- All widgets regardless of whether they natively support the dnd, or not, respond to drag related signals defined in Gtk::Widget#Signals. For your convenience I also list these signals in the following listing:
+ With the exclusion of the above mentioned exceptions ('drag-data-get' and 'drag-data-received' signals) for widgets that so not natively support dnd, all widgets regardless of whether they natively support the dnd, or not, respond to drag related signals defined in Gtk::Widget#Signals. For your convenience I also list these signals in the following listing:
drag-begin ............... self, drag_context
drag-data-delete ......... self, drag_context
- drag-data-get ............ self, drag_context, data, info, time
- drag-data-received ....... self, drag_context, x, y, data, info, time
+ * drag-data-get ............ self, drag_context, data, info, time
+ * drag-data-received ....... self, drag_context, x, y, data, info, time
drag-drop ................ self, drag_context, x, y, time
drag-end ................. self, drag_context
drag-leave ............... self, drag_context, time
drag-motion .............. self, drag_context, x, y, time
+
As you can see the widgets without their own Gdk::Window exhibit a limited set of dnd behaviours (actions). For this reason when you design your programs, that need dnd facilities with such widgets you need to provide your own code to handle drag signals and implement custom drag-and-drop actions. We will look closely at this in the following section revealing the promised 'button-to-label-dnd.rb'