ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 6日 (木) 12:52:45 JST
-------------------------
REMOTE_ADDR = 70.49.50.17
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -48,7 +48,7 @@
Normally, you have to set up source and destination widgets. There exists a plethora of methods to accomplish this. However, there are three different situations or circumstances in which you need to set up either source or destination widget for drag-and-drop management. Depending on the combination of the source and destination drag-and-drop widgets you are using in your application, there are many ways to set up (or, as you will soon see, perhaps not at all set up) these source and destination widgets.
- We can briefly point out the three different scenarios for setting up source and destination widgets as follows. Starting with those widgets that support dnd by design, we encounter those (1) for which you may simply start using the native dnd facilities without ever setting either the source or the destination widgets (for instance Gtk::TextView is such a widget). (2) Next from the same category we have such as the Gtk::IconView, or the Gtk::TreeView widget, with which you can use the default dnd behaviour with almost no extra programming work. And lastly, (3) the widgets without native drag-and-drop support for which, in order to use drag-and-drop facilities, you really need to register those widgets as source or destination widget or both.
+ We can briefly point out the three different scenarios for setting up source and destination widgets as follows. Starting with those widgets that support dnd by design, we encounter those (1) for which you may simply start using the native dnd facilities without ever setting either the source or the destination widgets (for instance Gtk::TextView is such a widget). (2) Next, from the same category we have such as the Gtk::IconView, or the Gtk::TreeView widget, with which you can use the default dnd behaviour with almost no extra programming work. And lastly, (3) the widgets without native drag-and-drop support for which, in order to use drag-and-drop facilities, you really need to register those widgets as source or destination widget or both.
We hope to look at all of these three situations.