| openqm début | |
| qu'
est ce qu' openqm ? qu'est ce que les sources ouverts ? qu'est qu'il y a de neuf dans les maj récentes ? applications et outils de développement contactez-nous
keyboard input problems
|
keyboard input problems
every line of terminal input from a telnet connection appears to have an ascii nul character in it
qm assumes that telnet conenctions start with binary mode disabled. if your terminal emulator works in binary mode but does not send the related telnet negotiation parameter, the nul characters that appear after every newline will be treated as data. the solution is either to turn off binary mode in the emulator or to upgrade to an emulator that supports binary mode negotiation.
the backspace key does not erase the character preceding the cursor
some terminals (e.g. wyse 50 and wyse 60) send the same character for the backspace key and the cursor left key. qm is unable to distinguish these and may interpret the backspace as a cursor left or vice versa depending on how the input data is being processed. if possible, either use a different terminal type or modify the code sent by the emulator for cursor left (and the corresponding terminfo entry) to somethign different. if this is not possible, deleting the terminfo definition for the cursor left key (kcub1) will ensure that the key is always interpretted as a backspace.
my cursor keys do not function correctly over a telnet connection
qm uses the terminfo library to identify control sequences sent by terminals when special keys are pressed. the usual reason for incorrect recognition of cursor keys is that the wrong terminal type has been selected. the standard microsoft telnet emulator provided with windows used to use a vt100 emulation. later versions are vt220 emulation.
alternatively, some vt100 terminal emulators have an option to send variations of the cursor key codes.
in either case, the problem is almost certainly that your terminal emulator does not match the terminal type selected using the term command.
my function keys, home, end, etc do not work correctly over a telnet connection
the standard microsoft telnet emulator provided with later versions of windows does not recognise the function keys. you will need to find an alternative terminal emulator if you need to use the function keys.
on windows 95, the caps lock key toggles all keys, not just the alpha keys.
this is a windows 95 bug in the windows readconsoleinput api. because microsoft has withdrawn support for windows 95, we consider this bug a dead issue and are no longer researching a solution. the following work-around will largely correct the problem for users still working with this operating system.
using the qm configuration editor, select the qm section. click on the add button. enter win95fix in the new parameter box and set a value of 1 in the value box. click on the set new value button followed by the save changes button.
users of qmterm should use the same procedure to add the win95fix parameter to the qmterm section of the configuration parameters.
this solution is not perfect as the escape key will not function correctly when caps lock mode is selected.
|