diff options
author | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2024-09-22 12:36:34 +0200 |
---|---|---|
committer | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2024-09-22 12:47:40 +0200 |
commit | 84cc45ebbdcd62a0bad33d65223a45dc146a0f07 (patch) | |
tree | 92542e77d61b3c7f30dcb9aa9028b1fa8e9240fb /src/interface.c | |
parent | 4ca4ba21ccfb6c415462d5a748e7dee5a82121e0 (diff) | |
download | sciteco-84cc45ebbdcd62a0bad33d65223a45dc146a0f07.tar.gz |
Curses: always wgetch() on a dummy pad, avoiding unnecessary wrefresh()
* This is especially important on platforms, requiring the wgetch()
poll workaround to detect CTRL+C (PDCurses/WinGUI).
wgetch(cmdline_window) would implicitly wrefresh(cmdline_window),
which resulted in additional flickering when pressing function keys.
This is no longer so important since key macros are processed
as an unity and the cmdline will be updated only after processing
all of the characters contained in them, ie. only once after the key press.
Still, there could have still been unwanted side effects.
At the very least, wgetch(input_pad) should be faster.
* The XTerm clipboard implementation was getch()ing on stdscr,
so potentially suffered from the same problem.
It should be tested again.
* Since keypad() is now always enabled even on netbsd-curses.
I assume that the function key processing bug in netbsd-curses
has been fixed by now. We are not building any releases with
netbsd-curses. But it should be retested.
* It does not resolve all flickering issues on PDCurses/WinGUI.
Both the command line and the Scintilla view still flicker near
the cursor. See
https://github.com/Bill-Gray/PDCursesMod/issues/322
Diffstat (limited to 'src/interface.c')
0 files changed, 0 insertions, 0 deletions