Windows Emoji Picker not recognised in `KeyCode::Char`

[axololly]

Describe the bug
When listening for char input, any emojis sent through the emoji picker are not picked up.

To Reproduce
Steps to reproduce the behavior:

1. Loop and print all Event::Key events
2. Use Win + . to open the emoji picker
3. Select an emoji
4. Nothing occurs in the terminal, other than losing and gaining focus

Expected behavior
A stream of KeyEvents containing the chars that make up the emoji selected.

OS
Windows 11

Terminal/Console
Windows Terminal

[himhimlo]

Yes, I am suffering from this issue too.
I have done some research and found that it has been there from long time ago.
Issue
And the author of that post has made a pull request for the issue but got no reply.
Pull Request

[axololly]

I think Crossterm needs to update its Windows API to detect inputs like this, since it seems to be missing out on quite a few important features.

I might even consider looking into Microsoft's edit and seeing what they do, since their app can take emoji picker input.

[himhimlo]

Yup I think so. And I have also tried look into their code.
And I found them using own terminal library instead of using crossterm;)

[axololly]

Yes. Microsoft's edit has zero dependencies with 18,000 lines of code under an "every byte counts" philosophy.

[himhimlo]

And m$'s team should be so familiar with win32 API XD

[himhimlo]

And it seems that the issue only happen in Windows Terminal but not in VSCode's embedded terminal.
I have traced crossterm's code and found the issue is because in Windows Terminal, Crossterm will read both key_down and key_up event of a unicode surrogate and try to decode with both which is incorrect.

You may take a look into this method in Crossterm's code.

[himhimlo]

In fact, I can fix the issue by just skipping the keydown event for surrogates.

[axololly]

@himhimlo Do you want to make a fork with these changes in them?

[himhimlo]

I think mine is only a workaround, not a complete solution, btw maybe I still try try to send them PR tmr, since I can see this issue affecting many places and very annoying...