notcurses_input.3: mention mouse events in bottom/right margins can show up #2233

This commit is contained in:
nick black 2021-10-05 05:34:06 -04:00
parent 5a06a27df7
commit 4c81a72bab
No known key found for this signature in database
GPG Key ID: 5F43400C21CBFACC

View File

@ -161,10 +161,11 @@ Only one thread may call into the input stack at once, but unlike almost every
other function in notcurses, **notcurses_get** and friends can be called other function in notcurses, **notcurses_get** and friends can be called
concurrently with **notcurses_render**. concurrently with **notcurses_render**.
Do not simply **poll** the input file descriptor. Instead, use the file Do not simply **poll** the file descriptor associated with **stdin** to test
descriptor returned by **notcurses_inputready_fd** to ensure compatibility with for input readiness. Instead, use the file descriptor returned by
future versions of Notcurses (it is possible that future versions will process **notcurses_inputready_fd** to ensure compatibility with future versions of
input in their own contexts). Notcurses (it is possible that future versions will process input in their own
contexts).
When support is detected, the Kitty keyboard disambiguation protocol will be When support is detected, the Kitty keyboard disambiguation protocol will be
requested. This eliminates most of the **BUGS** mentioned below. requested. This eliminates most of the **BUGS** mentioned below.
@ -190,6 +191,10 @@ future.
When the Kitty keyboard disambiguation protocol is used, most of these When the Kitty keyboard disambiguation protocol is used, most of these
issues are resolved. issues are resolved.
Mouse events in the top and left margins will never be delivered to the
application (as is intended), but mouse events in the bottom and right margins
sometimes can be if the event occurs prior to a window resize.
# SEE ALSO # SEE ALSO
**gettimeofday(2)**, **gettimeofday(2)**,