Add "al_get_render_state" #1583
Merged
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
SiegeLord
requested changes
Sep 28, 2024
SiegeLord
reviewed
Sep 28, 2024
SiegeLord
reviewed
Sep 28, 2024
|
Thanks! |
|
Sweet! I missed the merge notification on this one. I've already had several times where this would be useful. Thank you! |
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.
During some debugging, I noticed I didn't have access to the current render state, which would be helpful. This would be particularly useful in instances where different parts of a game system manage render state differently, and checking for possible leaky render state. The values for it seem to be stored in
ALLEGRO_DISPLAY.Some points to be aware of in this PR:
display. This implementation just has it return0with no warning or anything.