aboutsummaryrefslogtreecommitdiffstats
path: root/src/w32term.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/w32term.c')
-rw-r--r--src/w32term.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/w32term.c b/src/w32term.c
index 28861eea902..52c78b0558a 100644
--- a/src/w32term.c
+++ b/src/w32term.c
@@ -5401,7 +5401,7 @@ x_set_window_size (f, change_gravity, cols, rows)
5401 resize will happen asynchronously. But on Windows, the menu bar 5401 resize will happen asynchronously. But on Windows, the menu bar
5402 automatically wraps when the frame is too narrow to contain it, 5402 automatically wraps when the frame is too narrow to contain it,
5403 and that causes any calculations made here to come out wrong. The 5403 and that causes any calculations made here to come out wrong. The
5404 end is some nasty buggy behaviour, including the potential loss 5404 end is some nasty buggy behavior, including the potential loss
5405 of the minibuffer. 5405 of the minibuffer.
5406 5406
5407 Disabling this code is either not sufficient to fix the problems 5407 Disabling this code is either not sufficient to fix the problems
@@ -5524,9 +5524,9 @@ x_raise_frame (f)
5524 BLOCK_INPUT; 5524 BLOCK_INPUT;
5525 5525
5526 /* Strictly speaking, raise-frame should only change the frame's Z 5526 /* Strictly speaking, raise-frame should only change the frame's Z
5527 order, leaving input focus unchanged. This is reasonable behaviour 5527 order, leaving input focus unchanged. This is reasonable behavior
5528 on X where the usual policy is point-to-focus. However, this 5528 on X where the usual policy is point-to-focus. However, this
5529 behaviour would be very odd on Windows where the usual policy is 5529 behavior would be very odd on Windows where the usual policy is
5530 click-to-focus. 5530 click-to-focus.
5531 5531
5532 On X, if the mouse happens to be over the raised frame, it gets 5532 On X, if the mouse happens to be over the raised frame, it gets