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

[Feature Request]: better keyboard implementation #1791

Open
1 task done
kalle07 opened this issue Dec 4, 2024 · 2 comments
Open
1 task done

[Feature Request]: better keyboard implementation #1791

kalle07 opened this issue Dec 4, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@kalle07
Copy link

kalle07 commented Dec 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

ok i see all your inputs are mouse or pad optimized but i think most nerds using keyboard

lets say i have this

grafik

so i must click on every single number write a number and MUST hit enter
very unconfortable ;)

so why not once click on a number write a number and lets say with arrow keys i can move to the next number with out hiting enter to confirm the number ...

maybe also set, if no numbers are allowed, I can't write any
maybe set also "coma" same as "point"

and if i use "ctrl"+mouse and mark some nodes than hit right mouse-button (where ever) i can only bypass one node, if i hit "crlr"+B it works for all ... so thats inconsistent on the other hand ...

Proposed workflow

123

Additional information

No response

┆Issue is synchronized with this Notion page by Unito

@kalle07 kalle07 added the enhancement New feature or request label Dec 4, 2024
@webfiltered
Copy link
Contributor

This is a fairly significant undertaking, but something for keyboard is loosely planned. You're the first I've seen ask for widget keyboard nav, though - my plan was purely selfish. I currently scrape by with keyboard for only the first widget.

You've mentioned a few items in this PR, though, which will make it difficult to track. Would recommend that you split out each issue, so other people can see them.

@kalle07
Copy link
Author

kalle07 commented Dec 4, 2024

i see ;)
maybe ill wait some days

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

No branches or pull requests

2 participants