Debug Mouse coordinates not registering in Mystic BBS

[opicron]

I tried both Netrunner and SyncTerm mouse commands, they work with the main menu of Mystic. When awaiting the username on the login prompt and clicking on various coordinates no text is being output on the login prompt.

With fTelnet I am unable to make mouse coordinates work. When on the userlogin name prompt, clicking on various random coordinates do output the ansi command in the prompt.

• Could it be that, SyncTerm and Netrunner use different ANSI codes to send the mouse coordinates, very unlikely though?
  I tried switching the Sgr and Regular ANSI codes but both do not register. When clicking on random coordinates on the login prompt the ANSI code is being output on the login prompt.

• Is there a different way to send the escape code to the Mystic board which causes it not to be displayed in the login prompt?
  I tried sendind both ANSI codes though Connection.Send (and flush afterwards) and that results in the same behaviour.

• Mystic does send the ?1000h command which turns on Mouse commands in fTelnet. It doesnt send the ?1006h command.

For testing purposes: bbs.theforze.eu

[opicron]

Apparently in X10 mouse mode we have to send characters instead of numbers. And they have to be increased with 32. Im trying now this:

            this.onmousereport.trigger(
                '\x1B[M' +
                String.fromCharCode(32 + 0) + // button code (0 = left click)
                String.fromCharCode(this._MouseDownPoint.x + 32) +
                String.fromCharCode(this._MouseDownPoint.y + 32)
              );

No luck yet, but at least the output is not being shown on the login prompt.

[opicron]

And fixed, this is the correct X10 ansi for mouse down:

fTelnet/source/crt/Crt.ts

Line 1071 in 9dbbd71

this.onmousereport.trigger('\x1B[M' + String.fromCharCode(button) + String.fromCharCode(x) + String.fromCharCode(y));

                this.onmousereport.trigger(
                    '\x1B[M ' +
                    String.fromCharCode(this._MouseDownPoint.x + 32) +
                    String.fromCharCode(this._MouseDownPoint.y + 32)
                  );

And this is the correct code for mouse up:

fTelnet/source/crt/Crt.ts

Line 1239 in 9dbbd71

this.onmousereport.trigger('\x1B[M' + String.fromCharCode(button) + String.fromCharCode(x) + String.fromCharCode(y));

                this.onmousereport.trigger(
                    '\x1B[M3' +
                    String.fromCharCode(UpPoint.x + 32) +
                    String.fromCharCode(UpPoint.y + 32)
                  );

For proof: please visit bbs.theforze.eu and check main menu mouse commands.

For documentation X10 xterm:

https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Mouse-Tracking

Normal tracking mode sends an escape sequence on both button press and
release.  Modifier key (shift, ctrl, meta) information is also sent.  It
is enabled by specifying parameter 1000 to DECSET.  On button press or
release, xterm sends CSI M CbCxCy.

o   The low two bits of Cb encode button information:

              0=MB1 pressed,
              1=MB2 pressed,
              2=MB3 pressed, and
              3=release.

o   The next three bits encode the modifiers which were down when the
    button was pressed and are added together:

              4=Shift,
              8=Meta, and
              16=Control.

o   Cx and Cy are the x and y coordinates of the mouse event, encoded as
    in X10 mode.

[opicron]

Apparently I am on an older version as I see in your code the chars are already send correctly. If on mouseup it is sending [M3 we are golden, because 3 means released. That might be a small improvement/fix which was required. Now its sending the value of 'button', but that is (I believe) incorrect.

Edit: I updated and changed the mouseup event to send ESC[M3 and Mystic is correctly registering mouse events.

Ps: Your solution is very elegant, I love how you use number = '!'.charCodeAt(0) + UpPoint.y - 1; instead of +32.

[rickparrish]

Just to confirm, with the latest version of fTelnet are things working as-is, or are you saying you had to change the MouseUp event to send ESC[M3 instead of ESC[M# in order for it to work?

Because as far as I can tell based on the SyncTerm source, the MouseUp event also adds 32 to the button value like the MouseDown event does, so I would expect the button character in the MouseUp event to be 32+3=35 #, not a literal 3 character.

And I can't take any credit for the solution, that was how SyncTerm did it, and I also thought it was an elegant solution so kept the same style when implementing in fTelnet.

[opicron]

You are again correct =). I double checked the source and ESC[M# does indeed register.