Open noword opened 4 years ago
update: The Windows 10 pro was installed the old version prompt_toolkit. I guess the old version hasn't Windows10_Output yet.
update: The Windows 10 pro was installed the old version prompt_toolkit. I guess the old version hasn't Windows10_Output yet.
My prompt_toolkit version : 3.0.6
still has this bug.
I add raise
at line 133 , but it doesn't seem to be triggered.
Interesting this worked for you, I didn't see this when I posted #1232
From what I saw it looks like mouse support should be enabled on the input handle mode not the output.
It makes sense if you consider that Windows API is designed to allow nested windowed text UI.
My guess was that mouse events land on the output by default but can be disabled and are disabled on the input by default apparently in some versions of windows.
But I'll give this a try.
I tried this but it did not work for me.
I will work on it this weekend and see if my guess in the previous comment is correct.
Follow #1232
If I can get it working that way I'll make a pull request.
I use a computer installed Windows 10 enterprise ltsc 2019. Mouse is not responding on it.
It's weird,cause another computer installed Windows 10 pro is totally fine.
Finally I figure it out. In 'key_binding/bindings/mouse.py' line 133:
should be
Thank you for this great project.