Add strict pathfinding setting for looping courses - #559
Draft
mprussak wants to merge 1 commit into
Draft
Conversation
Adds a new setting "strictPathResume" to resume looping courses from the destination of the previous leg rather than searching for a new start point.
Author
|
Let me know what's preferred regarding the |
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.
Adds a new setting "strictPathResume" to resume looping courses from the destination of the previous leg rather than searching for a new start point. This new setting is off by default for backwards compatibility. I didn't see any reason to make it per-vehicle, so right now it's a global setting.
This addresses the inconsistent/unexpected behavior mentioned in #558
I'm marking this PR as a draft to call attention to the large diff in
translation_tr.xml. It looks like thesync_translationsscript is making some whitespace changes to older sections that weren't previously committed, and I'm not sure if I should use the cleaned up automatically generated version or hand-edit to preserve the original whitespace.