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

Add a keyboard button to automatically go to the nearest suggested building #1564

Open
expected-ingot opened this issue Sep 17, 2024 · 3 comments
Labels
feature-usability Issue or feature related to usability - something hard to do

Comments

@expected-ingot
Copy link

Description

Hello! There should be a keybind that goes to the nearest suggested building, so that you can edit quickly by accepting, and then maybe repositioning and then instantly jumping to the next one. It would help others contribute to OSM more efficiently.

@bhousel bhousel added the feature-usability Issue or feature related to usability - something hard to do label Sep 17, 2024
@jjiglesiasg
Copy link

I still suggest having a feature to resize (up and down) the buildings once validated, not just to move them... (ID has such feature by the way)

@bhousel
Copy link
Contributor

bhousel commented Dec 18, 2024

Update, per #1336 (comment) -

While this isn't a button or shortcut that jumps to the next building, it can make mapping a lot more efficient - try it out in the canary build and let me know what you think.

I did this today, and tested a bunch with Rapid to see how it feels. It can really improve mapping efficiency!

When a Rapid feature is selected or hovered the following will apply:

  • If feature was selected and we hit A, accept and select the newly added feature
  • If feature was just hovering and we hit A, hover (but don't select) the newly added feature
  • If we hit M to move or R to rotate, accept, then select and enter that mode instead

@jjiglesiasg
Copy link

jjiglesiasg commented Dec 18, 2024

I tested in Riberalta - Bolivia and the floating over and acceptance do not work as described, unless you start selecting an inferred element and accepting it, from that point works the floating and acceptance. But you need to repeat this process again and again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-usability Issue or feature related to usability - something hard to do
Projects
None yet
Development

No branches or pull requests

3 participants