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: osm[at]mocacher.de [Submitted to the original trac issue database at 4.09pm, Monday, 12th January 2009]
When moving existing nodes to a GPX track point's position (especially with auto snap), the user is asked if the points should be merged.
Merging nodes in this case is not useful since changing the GPX point position is not wanted and merging the existing node with the track point is not necessary.
This could be fixed by making GPX tracks read-only (configurable), or by not applying merge magic to GPX nodes at all.
The text was updated successfully, but these errors were encountered:
Author: koying [Added to the original trac issue at 7.08pm, Tuesday, 31st March 2009]
(In [14373]) ADD : Support for discardable dialogs/messageboxes (fixes #1487)
FIX : Do not automerge GPX nodes (fixes #1486)
FIX : Proper clipping via Boost's geometry template library
Reporter: osm[at]mocacher.de
[Submitted to the original trac issue database at 4.09pm, Monday, 12th January 2009]
When moving existing nodes to a GPX track point's position (especially with auto snap), the user is asked if the points should be merged.
Merging nodes in this case is not useful since changing the GPX point position is not wanted and merging the existing node with the track point is not necessary.
This could be fixed by making GPX tracks read-only (configurable), or by not applying merge magic to GPX nodes at all.
The text was updated successfully, but these errors were encountered: