Completely remove the GdxRenderer #5813
Merged
+0
−7,449
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.
Identify the Bug or Feature request
Completes #5780
Description of the Change
With the final change to 1.18, users can no longer enable the LibGDX renderer. Internally, the renderer is not actually used for anything either. Finally, development of the LibGDX renderer has moved to the
feature-gdx-renderer
branch for the time being. So that devs don't have to worry about updating LibGDX as they make other changes, this PR removes all the remaining GDX code from the codebase.It leaves in a few bits of GDX support, notably the
ZoneRenderer
still checks of the GDX renderer is active before try to draw itself. This check is alwaysfalse
, but remains in the hopes of adding theGdxRenderer
back in the future.Possible Drawbacks
None
Documentation Notes
N/A
Release Notes
N/A
This change is