Skip to content
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

Add parameter force_stop_on_cancel to send a zero-speed command on canceling navigation #173

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

corot
Copy link
Collaborator

@corot corot commented Feb 17, 2020

Following discussion on e4cdbb9 and #171.

Actually, I'm realizing that we have not documented all these parameters... So won't be usefull unless inspecting the code, what is probably a lot to ask.

@corot corot requested a review from spuetz February 17, 2020 13:45
@corot corot self-assigned this Feb 17, 2020
@spuetz
Copy link
Collaborator

spuetz commented Mar 24, 2020

Shouldn't the default of force_stop_on_cancel be true to keep the same behaviour as before?

@corot
Copy link
Collaborator Author

corot commented Mar 24, 2020

Shouldn't the default of force_stop_on_cancel be true to keep the same behaviour as before?

Well, we added that stop on 16 October: e4cdbb9#diff-7bfab1323bf81df50a6c81b1a4965dacR272

So the default behavior has been same as false for much longer. And doing nothing is typically a more predictable behavior

@spuetz spuetz merged commit eb9d6a6 into master Mar 24, 2020
@Timple Timple mentioned this pull request Apr 24, 2020
@spuetz spuetz deleted the force_stop_on_cancel branch May 25, 2020 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants