core/avm2: Minor fix to construction of children that were placed on the first frame #22239
Conversation
This file contains hidden or 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
This change should not be observable, as no other `DisplayObject` subclasses can have timeline children
Also make them standalone functions instead of associated methods. Previously, they were associated methods on `TDisplayObject`, but they didn't actually access the `DisplayObject` they were called on
…antiation Often, `MovieClip`s have children that are placed before the `MovieClip`'s AVM2 side is allocated and instantiated. These children will be instantiated in the `super()` constructor (specifically, the `Sprite.constructChildren` call), rather than in-line with normal frame construction. However, if the `super()` constructor is /never/ called, these children will never be instantiated. This commit adds a flag that is set on such early children. Children with this flag set will never have `construct_frame` called on them during normal frame construction. Also add test coverage
Lord-McSweeney
added
waiting-on-review
Molisson
approved these changes
Nov 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The first two commits are not observable by code (except in stack traces that will now include
Sprite.constructChildren). The third commit fixes a minor issue with child construction-construct_frameis called on the children of aMovieClipeach frame, except on the first. This ensures children that were placed earlier in the frame lifecycle are properly instantiated. On the first frame of aMovieClip, the constructor forSprite(super()in a subclass) callsSprite.constructChildrento manually construct each child that was placed on the timeline in the first frame. This PR makes sure that these first-frame children are never constructed by the usual "construct_frameon every frame" logic by setting a newFRAME_CONSTRUCT_SKIPPEDflag on them.Closes #2916