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

[FR]: Add option to, or disable selecting messages by typing letters; Conflict with keyboard shortcuts #484

Closed
tonebacas opened this issue Sep 4, 2021 · 8 comments
Assignees
Labels
Component-Feed-List Component-Message-List Status-Fixed Ticket is resolved. Type-Enhancement This is request for brand new feature.
Milestone

Comments

@tonebacas
Copy link

Brief description of the feature request

Having the ability to perform certain actions using keyboard shortcuts does not mesh well with the ability to select messages by typing in letters/words present in the title of an article -- there's already a search feature that lets the user filter messages based on the presence of certain letters/words.

When I press a key, I don't wish to accidentally scroll and select a different message from the one I was reading at the time. Instead, I wish the perform the action that key might have assigned to it.

@tonebacas tonebacas added the Type-Enhancement This is request for brand new feature. label Sep 4, 2021
@martinrotter
Copy link
Owner

@tonebacas
I see. That seems like a valid request. Accepting. Will add this perhaps as option.

@martinrotter
Copy link
Owner

@tonebacas Now, can you write exactly which keyboard shortcuts/gestures are problematic?

@tonebacas
Copy link
Author

When you click on any message and then press any alpha-numeric key that is not associated with a keyboard shortcut command, the view will scroll to and select the first message that starts with the character you typed. For example, if you press G, and it isn't used for any command, the first message which title starts with G will be selected. And this happens without using the search box.

In my particular case, I have the keys Q, W, E, R, A, and S associated to some commands, so as I use those keys, no unintentional scrolling/selecting with happen. However, I'd like to prevent any unintentional action from taking place by disabling the behavior I've described previously.

@martinrotter
Copy link
Owner

@tonebacas OK, what keys should be only allowed in "restricted" mode - only arrow keys + modifiers (CTRL/ALT/META)? Or some extra additional keys like PGDN/PGUP/DELETE/HOME?

@martinrotter
Copy link
Owner

fixed in latest dev. build, please test in 20 minutes

image

@martinrotter
Copy link
Owner

if feature is enabled, only basic shortcuts will work like arrows, DELETE, etc. test and let me know

@tonebacas
Copy link
Author

I'm sorry, but I could no test the change. I will wait for the next release build.

@martinrotter
Copy link
Owner

@tonebacas why, you can just download it the same way as release build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component-Feed-List Component-Message-List Status-Fixed Ticket is resolved. Type-Enhancement This is request for brand new feature.
Projects
None yet
Development

No branches or pull requests

2 participants