Closed
Conversation
In MessageHandlers::HandleGetP changed the format of the returned data.
Modifications on the getPOSI methods to handle doubles and floats.
Modified the a C test function to test correctly with the new double getPOSI
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.
Overview
Updated the XPlaneConnect Plugin and APIs (Java, Matlab, Python and C) to deal with latitude, longitude and altitude positions in double precision float format. The tests for the C and Python API were updated as well.
Caution
PS
If you prefere I could create a new function similar to the one that returns the position and orientation in 32bit floats to handle doubles (both in the plugin and in the APIs). This way the backwards compatibility would be maintained.