Subj : Re: Mouse support in Netrunner2 (or Mystic?) To : g00r00 From : Rob Swindell Date : Sun May 17 2020 07:31 pm Re: Re: Mouse support in Netrunner2 (or Mystic?) By: g00r00 to Rob Swindell on Sun May 17 2020 09:35 pm > RS> However, when testing with Netrunner2, an upper-left left-button click > RS> sends this: > RS> 27 1b > RS> 91 5b '[' > RS> 77 4d 'M' > RS> 48 30 '0' > RS> 41 29 ')' > RS> 41 29 ')' > > RS> What mouse protocol is this and do you have a reference document? > > Hey Rob, > > I'd be happy to (try to) help! > > The latest NetRunner is beta 19 which uses either XTERM(?) or maybe VT200(?) > mouse support. I used whatever the default was in PUTTY at the time so that > it'd be compatible with Mystic "out of the box". I have netrunner2 beta 18 which seems to still the latest available for download from http://mysticbbs.com/downloads.html. Is there some other download location for beta 19? > I used to have a bookmark that had a reference but I can't seem to find it > at the moment. I read through my code and I did have some source code notes > that I can pass along, and a chunk of code from PUTTY that can be used as a > reference to its various mouse modes. > > (Some observations that I just made by looking at my code:) > > (It looks like the X/Y coordinates are just the ascii character > corresponding to the X/Y coordinate with with +32 added to it to avoid > conflict with low ascii control characters. Right. So upper left should be "!!", not "))" as is being sent by Netrunner2 beta 18. > So coordinates 1, 1 would be > represented as Ascii#33;Ascii#33. Yup, that jives with xterm and the "X10 compatibilityi mode" in the relevant docs I've located. > This means its limited to a terminal size > of 223x223 though which is something I overlooked at the time. Which is why the SGR-extended encoding is preferred. You can combine SGR-extended encoding (esc[?1006h) with the other mouse protocol modes. > It also > looks like Mystic sends esc[?1000h to the Unix terminal when running in Unix > to enable mouse reporting, so that seems like a clue we can Google to find > out officially what it is. In that doc I referenced, that mode is called "Normal tracking mode". In that mode, the X and Y coordinates should be encoded as in the X10 mode we talked about above. > NetRunner also translates a wheel spin to either > the up or down arrow ANSI escape sequence for max usefulness with > non-mouse-aware BBSes) Yup, noticed that. It's different than the standards, but works. digital man This Is Spinal Tap quote #41: Ian Faith: It say's "Memphis show cancelled due to lack of advertising funds." Norco, CA WX: 67.8øF, 69.0% humidity, 11 mph ENE wind, 0.00 inches rain/24hrs .