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.
Turns out mods integrating with or attempting to be compatible with Freecam may wish to compile against our classes and use our API.
e.g. FirstPersonModel compiles against Freecam v1.1.6 and uses the public API
Freecam.isEnabled()
that has (luckily) remained ABI compatible since before our initial commit.It may be useful to explicitly state the API status of various public methods, even if for no reason other than to make us think twice before changing the public API.
I've only done this for the main classes,
Freecam
andFreeCamera
for now. Ideally, we'd declare the API status of all public classes.One method I could only trace back to v0.2.2, which is the oldest release on GitHub and pre-dates the initial commit (AFAICT).