Minor usability fixes #21
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Tim,
As mentioned by email, a few small tweaks --they're individual commits, so I can split them into small PR if you don't want one or the other.
To clarify "duplicate point before converting it to waypoint": I mostly use GpsPrune for tracks I created myself (either planning or recording). When adding a name to a point, I would see the point be removed from the track, and the track who jump to skip the waypoint. I understand that's how GPX works, that "waypoints" and "trackpoints" are different objects and a waypoint doesn't need to be included in the track, but as a user that was annoying. As said it's a commit on its own, so I can carve it out of that PR if you want.