Mouse does not work in Windows Terminal

[pviotti]

When executing the example projects included in the repo on PowerShell or cmd in the Windows Terminal (this, here is the code) some anomalies happen:

• mouse is not tracked
• mouse click on menus does not work
• the element of the ListView (?) overflow

OS: Windows 10 1909
Terminal.Gui version: 0.24.0 (dev)

[BDisp]

I already checked and it's a very odd behavior indeed

[odalet]

Same behavior when running the sample inside WSL inside Windows Terminal:

However, the thumb in the vertical scroll bar is correctly rendered (whereas it is not in a standard command prompt):

Well, that may be a problem with Consolas (missing support for fallback characters?); once I change my command prompt font from Consolas to Fira Code, everything is fine:

[TylerLeonhardt]

Mouse support isn't supported in Windows Terminal but it's being worked on - confirmed:

https://twitter.com/cinnamon_msft/status/1237253970759782401?s=19

[tig]

PowerShell/ConsoleGuiTools#58

[tig]

Confirmed mouse is still not working in Windows Terminal 1.0 or Windows Terminal (Preview) Version: 1.0.1402.0.

[BDisp]

This really is a setback.

[tig]

This is the Windows Terminal bug, for clarity: microsoft/terminal#376

[tig]

Until this is fixed in Windows Terminal, there's nothing we can do about it.

For now I vote we do NOT make this a ship-blocker for 1.0.

I'm removing the 1.0 label. If you disagree please reply with why.

[tig]

New info:

microsoft/terminal#376 (comment)

Supposedly if we use VT-Style mouse support this will work today.

Are we using VT-Style or Win32? (I will try to look later today)

[BDisp]

Are we using VT-Style or Win32? (I will try to look later today)

Yes, in the NetDriver.

[tig]

Woot. I just did UICatalog -usc and mouse works in Windows Terminal 1.7+.

However netDriver is SO. DAMN. SLOW.

I wonder if it's possible to modify WindowsDriver to use VT-style mouse support while still using the console APIs for everything else?

[BDisp]

However netDriver is SO. DAMN. SLOW.

Yes, unfortunately.

I wonder if it's possible to modify WindowsDriver to use VT-style mouse support while still using the console APIs for everything else?

Yes, maybe it's a possibility.

[tig]

As of Windows Terminal Preview 1.9, the mouse works with WindowsDriver!

It has some minor issues (double click seems too sensitive). But separate issues should be opened for those.

Closing this.

[BDisp]

I saw that's working yesterday, but not mouse movement. I hope they fix that too.

[BDisp]

Also the Enter key doesn't' work in the NetDriver, because they aren't exposing the Key property, from ConsoleKeyInfo. So, Key = 0 instead of "Enter". So, reading from KeyChar = 13 '\r', is interpreted as Ctrl+M.