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
Display the Location Panel by default #9469
Comments
In what way, because it all it does is just list co-ordinates and an address? Someone else could argue the measurement and history panels are useful, should those be displayed by default as well? |
There are a ton of phone apps that display and/or log latitude and longitude, giving users useful information that they may then want to contribute to OSM.
I can see utility in the Measurement Panel in the editor, although I think being able to measure is more useful to end-users in the viewer.
History is super useful for editors in some cases, but not nearly as common as the others.
…------- Original Message -------
On Monday, January 23rd, 2023 at 07:05, Michael Booth ***@***.***> wrote:
> Location Panel can be super helpful for editing map data
In what way? Someone else could argue the measurement and history panels are useful, should those be displayed by default as well?
—
Reply to this email directly, [view it on GitHub](#9469 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A5KKDD2G3FXX56EHRGSNBT3WTZXXZANCNFSM6AAAAAAT7CCEK4).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Don’t think the feature is useful. Different users have different screens, I do not wish to see anything like this occupying the screen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The Location Panel can be super helpful for editing map data, but the only way to invoke it currently is to press CTRL + SHIFT + L (which is poorly documented).
This feature request is to show the Location Panel by default on the editor.
Screenshots
No response
The text was updated successfully, but these errors were encountered: