feat: add Runtime.BEFORE_STEP event and use it for frame-synchronized broadcasts in meshV2 #51
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.
Summary
This PR adds a new
Runtime.BEFORE_STEPevent to Scratch VM and modifies the Mesh V2 extension to use this event for frame-synchronized broadcasts.Changes
BEFORE_STEPevent constant and emission at the beginning of each_step().MeshV2Serviceto listen forBEFORE_STEPevent.setTimeout-based broadcast scheduling with apendingBroadcastsqueue.processNextBroadcast()which executes one queued broadcast per frame step.Purpose
In Mesh V2 batch event sending, receiving multiple events in a short interval previously caused multiple broadcasts to fire in the same frame. Due to Scratch VM's behavior, this would restart the same message's scripts, causing processing to be lost. By synchronizing broadcasts with frame steps (one per frame), we ensure every event is correctly processed.
Related Issue: smalruby/smalruby3-gui#475
Related Issue: smalruby/smalruby3-gui#473