diff options
| author | Po Lu <luangruo@yahoo.com> | 2022-09-24 16:27:42 +0800 |
|---|---|---|
| committer | Po Lu <luangruo@yahoo.com> | 2022-09-24 16:30:37 +0800 |
| commit | 54876bf498f5e6b4f7a66a051b105c3ddd308945 (patch) | |
| tree | 48de4eac951b7cb9866d37011faeb55ee260ff0d /test/lisp/emacs-lisp/vtable-tests.el | |
| parent | 767a10cc63de8ce9f85ac688be33555278b4f3fb (diff) | |
| download | emacs-54876bf498f5e6b4f7a66a051b105c3ddd308945.tar.gz emacs-54876bf498f5e6b4f7a66a051b105c3ddd308945.tar.bz2 emacs-54876bf498f5e6b4f7a66a051b105c3ddd308945.zip | |
Reduce complexity of scroll bar window protection code
It turns out my previous theories of why ClientMessages were
generated were wrong, and they are just generated so we can set
finish to X_EVENT_GOTO_OUT to have them delivered immediately.
This allows for the code to be simplified greatly, by not
unpacking pointers to the raw window into the client messages.
* src/xterm.c (x_unprotect_window_for_callback): Return the
window removed from the queue, or nil if none.
(x_scroll_bar_to_input_event)
(x_horizontal_scroll_bar_to_input_event): Use window provided by
x_unprotect_window_for_callback.
(handle_one_xevent): Pass dpyinfo to functions that need it.
(x_free_frame_resources): Remove "first scroll bar request"
code.
* src/xterm.h (struct x_display_info): Likewise.
Diffstat (limited to 'test/lisp/emacs-lisp/vtable-tests.el')
0 files changed, 0 insertions, 0 deletions