Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUTTON1_DOUBLE_CLICKED is being returned while mouseinterval(0) #130

Open
GiorgosXou opened this issue Dec 23, 2021 · 4 comments
Open

BUTTON1_DOUBLE_CLICKED is being returned while mouseinterval(0) #130

GiorgosXou opened this issue Dec 23, 2021 · 4 comments

Comments

@GiorgosXou
Copy link
Contributor

while BUTTON1_CLICKED and BUTTON1_TRIPLE_CLICKED events are being ignored\replaced with _PRESSED\_RELEASED events when mouseinterval(0) (as they should), for some reason BUTTON1_DOUBLE_CLICKED event is being returned instead of _PRESSED\_RELEASED.

@wmcbrine
Copy link
Owner

I assume this is specific to one platform (wincon)?

@GiorgosXou
Copy link
Contributor Author

yes

@wmcbrine
Copy link
Owner

In the Windows Console, BUTTON_DOUBLE_CLICKED is actually returned directly as an event by the operating system, rather than being composed by PDCurses out of press/release events. I'm not sure how this can be changed.

@Bill-Gray
Copy link
Contributor

At some point, it may be possible to use VT/xterm control sequences for mouse (and keyboard) input. Those sequences return a stream of presses and releases, leaving it up to you to synthesize clicks and double-clicks and triple-clicks.

At present, I think Microsoft's concept of such sequences appears to remain is a little sketchy. I've seen it return two consecutive presses when you've done a press and a release, or that the released button differs from the one you pressed. (Should note I've not investigated all that thoroughly. It's also possible that Microsoft, having "embraced" VT/xterm sequences, is now "extending" them.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants