|
drag-and-drop signal propagation: msg#00047gnome.gtk+.python
Do drag-and-drop signals not propagate to parent widgets like other signals? Nested widgets can attach signal handlers to a signal, and then return gtk.FALSE if they want the signal to be propagated to their ancestors But returning gtk.FALSE from a signal handler attached to a drag-and-drop signal (specifically, 'drag_motion') does not seem to propagate the signal to parent widgets. Is there some way to force DND signals to propagate to parent widgets? Perhaps I am really stupid and just missing something important. I'm including some sample code with a series of nested widgets that demonstrates this. Clicking anywhere propagates the click signal to all parent widgets. But dragging "middle" over anything only raises the signal on the current widget. matt ps. I assume that there is no built-in way to have a scrolled window containing drag targets automatically scroll as you drag a drag-source over it...
pygtk mailing list pygtk@xxxxxxxxxx http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: behaviour of window.present() on different WM: 00047, Elijah Newren |
|---|---|
| Next by Date: | Re: codegen documentation?: 00047, Tiago Cogumbreiro |
| Previous by Thread: | behaviour of window.present() on different WMi: 00047, Gian Mario Tagliaretti |
| Next by Thread: | Re: drag-and-drop signal propagation: 00047, Matt Chisholm |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |