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

Be sure all shortcuts have corresponding 'longcuts' in the menus #6397

Closed
jidanni opened this issue May 21, 2019 · 3 comments
Closed

Be sure all shortcuts have corresponding 'longcuts' in the menus #6397

jidanni opened this issue May 21, 2019 · 3 comments
Assignees
Labels
touch-stylus An issue with touchscreen or pen input
Milestone

Comments

@jidanni
Copy link
Contributor

jidanni commented May 21, 2019

The Keyboard shortcuts should all be real shortcuts.
I.e., they all should have corresponding "longcuts".
i.e., they should all be items already available in various menus, not standalone.
Not only would users be able to find them easier when looking among related items in the menus,
but that would make them available in cases when the shortcut was unusable (#5306).

@bhousel
Copy link
Member

bhousel commented May 21, 2019

I agree that we should not over-rely on keyboard entry, for eventual touch/mobile device support.
We'll think about how to best do this over the next few months as we plan out iD v3.

@bhousel bhousel added the touch-stylus An issue with touchscreen or pen input label May 21, 2019
quincylvania added a commit that referenced this issue Sep 9, 2019
Reword imagery problem link label (close #6820)
@quincylvania quincylvania added this to the 2.18.0 milestone Jun 12, 2020
@quincylvania quincylvania self-assigned this Jun 24, 2020
@quincylvania
Copy link
Collaborator

I added toggle buttons for all the panels that were shortcut-only: Background, Location, History, Measurement. I also did #2508, so copy and paste of features can now be performed without a keyboard.

While there are still some shortcuts that don't correspond directly to UI controls (zoom in/out by a lot, nudge features with arrow keys, select first/last/next vertex in a way), these are all things users can essentially accomplish via other interactions.

We should continue to pursue feature parity no matter what combination of input devices the mapper is using. See also #7713.

@l29ah
Copy link

l29ah commented Jun 5, 2023

It seems to me like the Find features matching search text thing is now shortcut-only, and i couldn't even trigger it with a shortcut: Ctrl-F triggers Firefox's text searching box, not iD's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
touch-stylus An issue with touchscreen or pen input
Projects
None yet
Development

No branches or pull requests

4 participants