Quantcast
Channel: All Open Tickets - Tera Term on OSDN
Viewing all articles
Browse latest Browse all 2128

mouse wheel events not translated to cursor keys - Tera Term Ticket #39405 on OSDN

$
0
0

mouse wheel events not translated to cursor keys

Eröffnet am: 2019-07-17 02:07

Letztes Update: 2019-07-26 13:14

Auswertung:(Anonym)Verantwortlicher:(Keine)
Priorität:5 - MittelMeilenstein:(Keine)
Typ:FehlerSchweregrad:5 - Mittel
Komponente:Tera TermStatus:Offen
LösungWorks For Me

Einzelheiten

i've been trying to configure teraterm so that mouse wheel events translate to VT cursor up/down key escape sequences. so far, zero success. the problem appears to be that the TranslateWheelTo Cursor setting in teraterm.ini is being ignored, and taken as always being set to false.

the sequence i've been using to enable the mouse is as follows:

ESC [?1000h
ESC [?1h

the first line (...1000h) turns on mouse reporting - mouse click events are reported correctly. the second line (...1h), as far as i can tell, should enable 'application cursor mode', which should cause the mouse wheel to NOT scroll the TeraTerm window, but instead send cursor up/down escape codes. instead, the window just continues to scroll. note that i do see the cursor keys themselves return alternate cursor escape sequences (ESC OA etc instead of ESC [A etc) as expected

is this a bug, or am i missing something else?

cheers, rob :-) rozee@mail.com

Letzte Aktualisierung für dieses Ticket

2019-07-26 13:14 Aktualisiert von: robert-rozee

Kommentar

followup:

i think i can now understand how TeraTerm is working.

ESC [?1h changes cursor key responses from ESC "[A" etc to ESC"OA" etc. it also turns on mouse wheel to cursor key (original) sequence translation. ie, mouse wheel generates ESC "[A". mouse wheel translation can be considered a 'later' addition in that traditional terminals didn't have mouses.

ESC [?1000h inhibits the mouse wheel generating cursor key sequences, instead (if the mouse mode used supports it) enabling mouse wheel reporting as button 4/5 events.

as such, there is no way to have BOTH (a) mouse click reporting AND (b) mouse wheel translation to cursor key sequences at the same time. none of the documention makes this entirely clear, and the matter is confused by slightly different terms being used to describe the same thing.

might i suggest reworking this page: https://ttssh2.osdn.jp/manual/en/usage/tips/appkeypad.html to read "Application cursor mode

In this mode, the arrow keys do not send the same key sequences. For example, UP ARROW sends <ESC>OA sequence. Also, IF NO MOUSE MODE HAS BEEN SELECTED, Tera Term would send UP ARROW or DOWN ARROW key sequence instead of scrolling through the window by rotating the mouse wheel. "

also, adding a third option to the setting:

TranslateWheelToCursor = on | off | forced

where if set to FORCED then mouse wheel translation to cursor key sequences always occur, irrespective of any mouse mode setting.

i believe this ticket can now be marked as 'resolved'.

cheers, rob :-)


Viewing all articles
Browse latest Browse all 2128