diff options
author | Po Lu <luangruo@yahoo.com> | 2022-05-22 12:22:44 +0000 |
---|---|---|
committer | Po Lu <luangruo@yahoo.com> | 2022-05-22 12:23:51 +0000 |
commit | 4c1af80322145159530a057d97a8828318e560c8 (patch) | |
tree | f927ff231db8d351c9e16831268ae6ae8fc756c1 /src/haikuterm.c | |
parent | 2b63fabcd3a42ce336400909ca0fb09ec23a88ba (diff) | |
download | emacs-4c1af80322145159530a057d97a8828318e560c8.tar.gz |
Clean up Haiku code
* src/haiku_support.cc (movement_locker, class EmacsWindow)
(MouseMoved): Delete `movement_locker' and associated hack,
since it's superseeded by some code in haiku_read_socket.
(key_map, key_chars, dpy_color_space, popup_track_message)
(alert_popup_value, grab_view, grab_view_locker)
(drag_and_drop_in_progress): Write comments and fix
initializers.
* src/haikuterm.c (haiku_read_socket): Update comment.
Diffstat (limited to 'src/haikuterm.c')
-rw-r--r-- | src/haikuterm.c | 23 |
1 files changed, 11 insertions, 12 deletions
diff --git a/src/haikuterm.c b/src/haikuterm.c index 47cffded48d..628ef2b0260 100644 --- a/src/haikuterm.c +++ b/src/haikuterm.c @@ -3348,18 +3348,17 @@ haiku_read_socket (struct terminal *terminal, struct input_event *hold_quit) previous_help_echo_string = help_echo_string; help_echo_string = Qnil; - /* A LeaveNotify event (well, the closest equivalent on Haiku, which - is a B_MOUSE_MOVED event with `transit' set to B_EXITED_VIEW) might - be sent out-of-order with regards to motion events from other - windows, such as when the mouse pointer rapidly moves from an - undecorated child frame to its parent. This can cause a failure to - clear the mouse face on the former if an event for the latter is - read by Emacs first and ends up showing the mouse face there. - - In case the `movement_locker' (also see the comment - there) doesn't take care of the problem, work - around it by clearing the mouse face now, if it is - currently shown on a different frame. */ + /* A crossing event might be sent out-of-order with + regard to motion events from other windows, such as + when the mouse pointer rapidly moves from an + undecorated child frame to its parent. This can + cause a failure to clear the mouse face on the + former if an event for the latter is read by Emacs + first and ends up showing the mouse face there. + + Work around the problem by clearing the mouse face + now if it is currently shown on a different + frame. */ if (hlinfo->mouse_face_hidden || (f != hlinfo->mouse_face_mouse_frame |