aboutsummaryrefslogtreecommitdiffstats
path: root/src/empathy-map-view.h
diff options
context:
space:
mode:
authorSjoerd Simons <sjoerd.simons@collabora.co.uk>2010-02-15 20:05:09 +0800
committerSjoerd Simons <sjoerd.simons@collabora.co.uk>2010-02-15 22:21:24 +0800
commit6b4d4954a4231209d261ced4ae0140ae11de6814 (patch)
tree6b5c8f189d994d769e45cdc5a2c5e4216b395bcb /src/empathy-map-view.h
parentd132874edb6b5af1a2755e006db4c87355a0d206 (diff)
downloadgsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar.gz
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar.bz2
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar.lz
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar.xz
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.tar.zst
gsoc2013-empathy-6b4d4954a4231209d261ced4ae0140ae11de6814.zip
Make the ChatWindow handle dropping items itself
Both GtkNotebook and EmpathChatWindow take action when drag-data-received is signalled (moving the tab or adding a contact). Drag data is received after the program has asked for it, usually when a drop occurs. Now this can be done in two ways 0) Handle the drop signal yourself and call gtk_drag_get_data yourself or 1) set GTK_DEST_DEFAULT_DROP and let gtk call it for you. GtkNotebook takes option 0, EmpathyChatWindow decided to use option 1.. This causes all kind of strange issues as the drag data is now requested twice and thus the signal handlers are called twice causing all kinds of fun issues (trying to move a tab that's already moved etc). Change the drag dest flags to GTK_DEST_DEFAULT_HIGHLIGHT which provides some extra visual clues but is other harmless and handle drops directly. Also remove some cases where ChatWindow meddles with tab dragging as GtkNotebook will handle these for us
Diffstat (limited to 'src/empathy-map-view.h')
0 files changed, 0 insertions, 0 deletions