|
You can turn on the trace functionality (trace=trace.txt) and the look at the lines that say "@key XX", where XX is the decimal representation of the key received. This is shown in display.c. -brian On Wed, 29 May 2002, Buck Calabro wrote: > I'm not a PC guy of any sort (win* or *nix) so my attempts to decipher the > code that handles the keyboard has been futile. I use the Windows version > of TN5250. I was hoping to be able to map my keyboard in a configuration > file, but just trying to figure out what key is where has me beat. > > I'm looking at terminal.h and I see a list of #define's like: > #define K_SYSREQ 0401 /* curses KEY_BREAK */ > #define K_CLEAR 0515 /* curses KEY_CLEAR */ > #define K_REFRESH 0564 /* curses KEY_REFRESH */ > #define K_FIELDEXIT 0517 /* curses KEY_EOL (clear to EOL) */ > > Where can I find out where curses thinks these keys are? > > What I really want is the functionality that allows me to jump from 'word' > to 'word', which looks like curses KEY_SRIGHT but shift+arrow doesn't seem > to do it for me. I searched the web but found nothing but manpages about > the output from getch() and friends. > > Where can I go to find out what physical key equates to the various curses > key definitions? > --buck > _______________________________________________ > This is the Linux 5250 Development Project (LINUX5250) mailing list > To post a message email: LINUX5250@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250 > or email: LINUX5250-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/linux5250. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.