GNOME Bugzilla – Bug 576952
Allow scroll wheel scrolling during DND
Last modified: 2018-05-02 14:41:18 UTC
Please describe the problem: Hi, nautilus bug 434193 wants to be able to scroll the destination window/folder when DND'ing a file in nautilus. This is currently not possible because gtk+ grabs keyboard when DND (see bug 390312), but although gtk grabs the scroll event on dnd, there's no reason why it should not resend it to the widget that is the drag destination. That is what my patch does, listens to scroll events on DND and resend the event to the drag destination widget. For some limitations this only works when the source and destinations widgets belongs to same application, although could be different windows, like in the nautilus case. I think this is good enough as it fullfils the nautilus use case which happens to be the most common. Steps to reproduce: 1. Open two nautilus windows representing two folders, make sure second folder has enough files so the window has scrollbars. 2. Drag some file from first window to second window. 3. Now (without releasing the mouse button 1 and so dropping the file) use the mouse scrollwheel to scroll the second window content, so you can reach some unseen folder where to drop the file. Actual results: Nothing happens, mousewheel scroll events are ignored. Expected results: The nautilus window should receive the mouse wheel scroll events and thus scroll the content of the window. Does this happen every time? yes Other information:
Created attachment 131496 [details] [review] Patch to allow pass-by of scroll events from DND to drag destintation widget
When you test the patch in comment 1 with nautilus in icon view or compact view, you'll possibly see some black lines, that's a small nautilus bug for which I also put a patch in the blocked bug 434193. This paint problem does not happen in nautilus list view or in other applications (I tested gthumb thumbnails view).
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Still present in Gtk+ 3.22.26.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/314.