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

Long key timeout confuses only-key-combo #128

Open
GoogleCodeExporter opened this issue Apr 9, 2015 · 3 comments
Open

Long key timeout confuses only-key-combo #128

GoogleCodeExporter opened this issue Apr 9, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Set key timeout to 1 second
2. Press one after the other, SHIFT, CTRL, a
3. key-mon shows you pressed SHIFT+CTRL+a, when in fact you pressed them in 
sequence, not at the same time.

Also, if you press SHIFT or CTRL, and then quickly type 100 characters, they 
are all shown in key-mon, even only key-combo was active.

I think when only key-combo is active, key-mon should only show keys when they 
are pressed NOW, not if they were pressed during the last second.

It would also be very helpful to be able to define what is a key-combo. In my 
programmer's Dvorak keyboard to get a "6" I press "SHIFT+]". That's not a 
key-combo for me, and it's distracting for the people watching video tutorials 
about programming to see key-mon active each time I type a number. I type lots 
of numbers :) I would like that pressing CTRL or ALT is a requirement to 
trigger key-mon :)

Thanks!

Original issue reported on code.google.com by [email protected] on 7 Jul 2013 at 1:01

@GoogleCodeExporter
Copy link
Author

The long key timeout was, admittedly, a poorly thought out afterthought.
I need to have a way of grouping combinations visually [Ctrl+A] vs [Ctrl] [A].

Original comment by [email protected] on 7 Jul 2013 at 3:19

@GoogleCodeExporter
Copy link
Author

I thought the timeout was a variable to indicate for how long to display the 
information but I'm not sure. Is that its purpose?

I looked at the source code and noticed that it's possible to check if keys are 
currently pressed or not. I think that's what's needed to make it work the way 
I need.

Ideally, I would like to create a list of rules of what a combo is. Not just 
SHIFT || ALT || CTRL, but something more precise. For example, I don't need to 
show which keys I pressed when I selected text using CTRL+SHIFT+LEFT. I do a 
lot of text selection, and displaying that is too much info. I don't know if 
it's a lot of work, but I would like to set rules like: (CTRL || ALT) && 
(A-Z,ENTER,F1-F12).

I think this depends very much on the kind of software you are screencasting. 
For something like Gimp, probably each key press is important. But for talking 
about source code editing, you would like to skip most of the key presses.

If anyone gives me indications of which files should be edited I may try to do 
this myself.

Original comment by [email protected] on 8 Jul 2013 at 11:46

@GoogleCodeExporter
Copy link
Author

Sorry, my mistake, I was confusing with "old keys".

Looks like the code should be in key_mon.py all related to timeout_sec.
Not sure why there is some commented out code there, not something I normally 
do.

Original comment by [email protected] on 8 Jul 2013 at 8:40

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

No branches or pull requests

1 participant