You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Mueck [Submitted to the original trac issue database at 2.25am, Sunday, 19th December 2010]
Yesterday I have to change some
name=X-harbour
natural=water
source=Bing
to
name=X-harbour
source=Bing
waterway=dock
So
I clicked onto key field "natural"
changed it to waterway
Return
"water" value field is ready to editing
... but it is displayed after the key "source"!
If I changed it to "dock" (and may be Return) and click onto the map, I got the result:
name=X-harbour
source=Bing
waterway=water
May be the reason of it, that waterway is sorted alphabetically at once? Index of field changes at once, so typing "dock" is lost?
If I don't click onto the map to leave editing but hit Return, key field "waterway" is again ready for editing, Return without editing, value field "water" is ready for editing, changed to "dock" Return and I got the right result ...
The text was updated successfully, but these errors were encountered:
Reporter: Mueck
[Submitted to the original trac issue database at 2.25am, Sunday, 19th December 2010]
Yesterday I have to change some
name=X-harbour
natural=water
source=Bing
to
name=X-harbour
source=Bing
waterway=dock
So
... but it is displayed after the key "source"!
If I changed it to "dock" (and may be Return) and click onto the map, I got the result:
name=X-harbour
source=Bing
waterway=water
May be the reason of it, that waterway is sorted alphabetically at once? Index of field changes at once, so typing "dock" is lost?
If I don't click onto the map to leave editing but hit Return, key field "waterway" is again ready for editing, Return without editing, value field "water" is ready for editing, changed to "dock" Return and I got the right result ...
The text was updated successfully, but these errors were encountered: