-
Notifications
You must be signed in to change notification settings - Fork 8
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
Manual Content: surface_reset_target() page wording could be made more accurate #8573
Comments
YYBartT
added a commit
to YoYoGames/GameMaker-Manual
that referenced
this issue
Dec 10, 2024
… accurate YoYoGames/GameMaker-Bugs#8573 * Listed all possible drawing targets that surface_reset_target() can reset to * Changed the "Note" tag on the note to "Warning" (as the function will throw a fatal error in this case)
YYBartT
added a commit
to YoYoGames/GameMaker-Manual
that referenced
this issue
Dec 12, 2024
… accurate YoYoGames/GameMaker-Bugs/issues/8573 * Moved information on the surface_reset_target() page to the Drawing page * Added an introduction on the Drawing page, describing when GameMaker draws things * Also added a section on "Drawing Targets" * Linked to the "Drawing Targets" section from the surface_reset_target() page
YYBartT
added a commit
to YoYoGames/GameMaker-Manual
that referenced
this issue
Dec 13, 2024
… accurate YoYoGames/GameMaker-Bugs/issues/8573 Listed the possible draw targets on the surface_reset_target() page
Clarified that |
verified |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The entry states that "This function resets all further drawing from the target surface back to the screen."
More accurately, surface_reset_target resets the target surface to either the last target set with surface_set_target, or to the application surface.
The surface_set_target entry defines this behavior correctly.
Manual Link
https://manual.gamemaker.io/lts/en/GameMaker_Language/GML_Reference/Drawing/Surfaces/surface_reset_target.htm
The text was updated successfully, but these errors were encountered: