In a curses menu, if you type a digit to start a count, the cursor jumps to the spot on the screen where the hero is. Strange and very noticeable if that spot is covered by the menu, although I didn't notice it when working on digits as group accelerators (changes for that didn't trigger this). Despite the cursor_on_u location, it isn't related to the recent flush_screen/cursor_on_u changes either. In 3.6.x, curses used it's own count entry code. Early on with to-be-3.7 it was changed to use the core's get_count(), so uses a different routine to get next input character. And the curses edition of that routine deliberately positions the cursor at the hero's location on the assumption that it only gets called when the map window is active.
34 KiB
34 KiB