|
From: Tait <gnu...@t4...> - 2014-06-23 20:32:12
|
Ethan A Merritt <sf...@us...> said (on 2014/06/23): > Isn't it true that all terminals already do the necessary key-code > processing so that they can send key events to the core code in mouse.c? > > For example, does "mouselabels.dem" work on MSWin? That demo reads > keystrokes in the plot window, turns them into labels in the core code, and then > replots with the new label. If the demo works, it shows that keycodes including > the space-key are correctly transmitted to the core code. > > Ethan The mouselabels demo does work* on Windows in wxt and windows terms, although one cannot create a label containing a space (because the space brings up the console) or q (it is ignored). * for some value of "works"... The Windows terminal tends to eat keystrokes unless they're typed much more slowly than a normal typing pace. The wxt terminal places the red text on top of the black, making it impossible to read either, and sometimes (I haven't figured out how to replicate it on-demand) backspace doesn't work. Both seem to add an extra "\033" label after hitting ESC to end label input. None of the Windows builds have a qt terminal to try. |