aboutsummaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorPo Lu2022-05-28 08:55:13 +0800
committerPo Lu2022-05-28 08:55:13 +0800
commit5c07aed894f9822560eabc607674b22aaaaf4780 (patch)
tree82a8ad4a3f3868ee10db157b32f1f86d56f2fa11 /src
parent26588e9594e869d6e1d813ac4a77c035048be74d (diff)
downloademacs-5c07aed894f9822560eabc607674b22aaaaf4780.tar.gz
emacs-5c07aed894f9822560eabc607674b22aaaaf4780.zip
Fix x_dnd_movement_frame detection on GTK builds
* src/xterm.c (x_dnd_begin_drag_and_drop): Make sure movement frame is on the correct display.
Diffstat (limited to 'src')
-rw-r--r--src/xterm.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/src/xterm.c b/src/xterm.c
index efa153efca1..756f0308111 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -10637,7 +10637,11 @@ x_dnd_begin_drag_and_drop (struct frame *f, Time time, Atom xaction,
10637 if (event_display == FRAME_DISPLAY_INFO (f)) 10637 if (event_display == FRAME_DISPLAY_INFO (f))
10638 { 10638 {
10639#endif 10639#endif
10640 if (x_dnd_movement_frame) 10640 if (x_dnd_movement_frame
10641 /* FIXME: how come this can end up with movement frames
10642 from other displays on GTK builds? */
10643 && (FRAME_X_DISPLAY (x_dnd_movement_frame)
10644 == FRAME_X_DISPLAY (f)))
10641 { 10645 {
10642 XSETFRAME (frame_object, x_dnd_movement_frame); 10646 XSETFRAME (frame_object, x_dnd_movement_frame);
10643 XSETINT (x, x_dnd_movement_x); 10647 XSETINT (x, x_dnd_movement_x);