because it can be useful/desirable/necessary to know the potential data formats available in a DnD operation LONG before committing to the drop (e.g when controlling cursor appearance).On Mon, Jul 29, 2013 at 4:23 PM, Виталий Кирсанов <krokoziabla gmail com> wrote:
_______________________________________________Hello list.I don't understand the purpose of widget's destination target list. With the source target list it's quite clear: the widget which emits "drag-drop" signal can analyse the list of target entries of the source of DND transaction and choose and get data for one of them (BTW can it sequentially get data for multiple targets within the same transaction?). So the destination widget is the one to check the source target list.But who analyses the destination target list of a widget? I know that gtk_drag_dest_set() is needed for making the bame accept DND drops. But why then we need a whole list of targets for that? A flag could suffice. Or maybe GDK, before commiting the drop, compares the contents of source and destination target lists and seeks common entries, and once found notifies the widget about the drop occurred?BR, Vitaly Kirsanovskype: vkirsan
gtk-list mailing list
gtk-list gnome org
https://mail.gnome.org/mailman/listinfo/gtk-list