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

LocationRelay: Overload Constructor with option for LOCATION_ACCURACY_THRESHOLD Option #484

Closed
wants to merge 3 commits into from

Conversation

lordneeko
Copy link

The idea here is to keep current compatibility, but create ability for the LocationRelay class to be used with a "Desired Accuracy" value. It may be more or less accurate than the default (10.0f) but it gives the user the option based on their needs.

lordneeko added 3 commits May 8, 2018 11:52
for LOCATION_ACCURACY_THRESHOLD Option
fix constructor
LocationRelay: Overload Constructor with option
@lordneeko
Copy link
Author

Would love to see movement in this repo...

@billbonney
Copy link
Collaborator

billbonney commented May 28, 2018

You've made your change against a very old commit in the repo. It would be better if you applied for changes to HEAD of develop. (I know they are small, but it means you will get proper credit in the git history by doing that)

NOTE: its's good to submit one commit for this change you can use 'squash' to help you.

If you need help send me a message and I can help.

Thx 👍

@lordneeko
Copy link
Author

I committed against the LocationRelay file in the develop branch, which shows it is the branch with the latest changes... i don't understand how that's a very old commit.

@billbonney
Copy link
Collaborator

billbonney commented Jun 1, 2018

Sorry, my mistake. I have crated a new Pull Request with a only one commit for the change to make it easier to review the complete change see #485

@billbonney billbonney closed this Jun 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants