#3077 compass true heading is sometimes returned as greater than 360 degrees on Android #80
Conversation
This file contains 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
…hat it's never greater than 360 degrees.
|
reviewed. Accepting. |
|
Thank you, Don. On Wed, Jun 15, 2011 at 12:54 PM, donthorp <
|
dlifshitz-maca
referenced
this pull request
in dlifshitz-maca/titanium_mobile
Jun 19, 2012
TIMOB-9369: BlackBerry: merge BB fork with appcelerator branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ti.Geolocation sometimes produces true headings that are greater than 360 degrees. I'm assuming that titanium_mobile/android/modules/geolocation/src/ti/modules/titanium/geolocation/TiCompass.java on line 129 just needs a bit of modular arithmetic (% 360).