Move switching of screen's current bitmap to after layout updates #14184
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.
Currently video_manager::frame_update() updates the screen object by calling finish_screen_updates(), that calls screen.update_quads(), where the current m_curbitmap is set as the bitmap to be used by the frame texture. The code then switches the m_curbitmap pointer to the other bitmap available to blit the next frame. The execution returns to after the last call was made in video_manager::frame_update() and continues through the code. One of the remaining calls is machine().osd().update(), where the layout is rendered. If the layout contains a script that calls screen:pixels() to obtain the data of pixels in the frame, it won't get the data of the last frame. To make this work, these changes move switching of screen's current bitmap to after the layout is updated.