Activity

1. ghost added

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Jul 27, 2020
2. ghost added

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Jul 27, 2020
3. Mike Griese (zadjii-msft)

   added

   Area-InputRelated to input processing (key presses, mouse, etc.)Related to input processing (key presses, mouse, etc.)

   Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.

   Priority-1A description (P1)A description (P1)

   Product-TerminalThe new Windows Terminal.The new Windows Terminal.

   on Jul 27, 2020
4. ghost removed

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Jul 27, 2020
5. Mike Griese (zadjii-msft)

   added this to the Terminal v2.0 milestone on Jul 27, 2020
6. DHowett commented on Jul 27, 2020

   

   Dustin L. Howett (DHowett)

   on Jul 27, 2020

   Member

   More actions

   Huh. This doesn't exactly work in the traditional console either, and it was somewhat of a fluke that it worked in WT. It should, though.

   This is what I get if I peek at the key events coming out of WC into the traditional console:

   v 001 0010 002a 0000 ^@   00000010
   ^ 001 0010 002a 0000 ^@   00000000
   v 001 0000 0000 00f6 �    00000000
   ^ 001 00e7 0000 00f6 �    00000000
   ^ 001 004f 0018 006f o    00000000
   

   and here's what I'm getting over the tap:

   ␛[255;0;0;1;16;1_␛[255;0;0;0;16;1_

   that 255 definitely ain't right

   👀React with 👀1Reacted by Frank Blendinger
7. Dustin L. Howett (DHowett)

   removed

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Jul 27, 2020
8. samhocevar commented on Nov 26, 2020

   

   Sam Hocevar (samhocevar)

   on Nov 26, 2020

   More actions

   So, how should a third-party application send Unicode characters to Windows Terminal if SendInput() no longer works by default?
9. lhecker commented on Nov 26, 2020

   

   Leonard Hecker (lhecker)

   on Nov 26, 2020

   Last edited by lhecker

   Member

   More actions

   As far as I can see, this issue was fixed in #7900. I'll close this issue for now as WinCompose works just fine on my end with the latest WT version.

   The good thing is that I now finally understood, why we've been receiving weird key events, containing invalid scan codes, for third party applications employing SendInput: WT doesn't use TranslateMessage(Ex) properly. (I mean there's a very specific reason it doesn't... Namely the necessity to receive key events even for character keys.)

   👍React with 👍3Reacted by Sam Hocevar, Frank Blendinger and mordquist
10. Leonard Hecker (lhecker)

    closed this as completedon Nov 26, 2020
11. ghost added

    Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

    on Nov 26, 2020
12. mordquist commented on Nov 30, 2020

    

    mordquist

    on Nov 30, 2020

    Author

    More actions

    I can confirm that it works for me as well on Terminal 1.4 even with "experimental.input.forceVT" unset.
13. smooth038 commented on Apr 15, 2023

    

    Simon Larivière (smooth038)

    on Apr 15, 2023

    More actions

    I don't know if maybe this problem got recently reintroduced, but WinCompose currently does not work with any window terminal on my machine (cmd, powershell or windows terminal). When typing rightAlt ' a, it just outputs 'a and the compose key is ignored.

    I tried the "experimental.input.forceVT" setting, but it doesn't seem to do anything.

    Can anyone else reproduce this?
14. smooth038 commented on Apr 15, 2023

    

    Simon Larivière (smooth038)

    on Apr 15, 2023

    Last edited by smooth038

    More actions

    I just found the problem. It didn't work because I was running the terminals in administrator mode, but WinCompose did not have admin privileges. When WinCompose is run as admin, everything works fine.