-
Notifications
You must be signed in to change notification settings - Fork 221
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
Centralize basic math types and functions (part 5) #372
Draft
dimitry-ishenko
wants to merge
120
commits into
orbitersim:main
Choose a base branch
from
dimitry-ishenko-orbiter:math5
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Move them into the D3D9Client.
Some of the functions were taken over by the new vector templates. Others were removed or absorbed into D3D9Util.h.
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V().
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V().
Remove unnecessary _V().
Remove unnecessary _V().
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V().
Remove unnecessary _V().
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V().
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V(). Use new vector functions.
Remove unnecessary _V().
Remove unnecessary _V(). Use new vector functions.
For now it is kept inside the oapi namespace so as to keep compatibility with the existing addons.
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.
This is a fifth in a series of PRs meant clean up and centralize basic math constants, vectors and matrices. Currently these are scattered all over the project and many of them have overlapping functionality.
For example, there are
VECTOR3
andVECTOR4
types defined in the SDK (theOrbiterAPI.h
file). Then there areVector
andVector4
types defined in the Orbiter (theVecmat.h
file). There are alsoFVECTOR3
andFVECTOR4
which are equivalents ofVECTOR3
andVECTOR4
but with thefloat
data type. Each one of these classes overloads their own set of operators and defines their own versions of different functions. This results in messy and duplicate code.Similar situation exists for the matrices, and simple math constants eg, 𝜋, etc.)
The plan is to unite all these types and define a set of operator and function templates that are uniform and are shared by all these types. The steps are:
VECTOR4
type.VECTOR3
type.Vector4
andVECTOR4
.Vector
andVECTOR3
.FVECTOR2
.COLOUR3
andCOLOUR4
.FVECTOR3
.