Bugfix - Regression: PR #445 caused a blank screen on startup #456
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.
Issue: For apps that don't have an animation or initial event to trigger a dirty window, the screen will be blank until something triggers a dirty state.
Defect: Previously, before #445 , we had a
needsRender
value on the app instance that was set totrue
on startup, and anytime an action was dispatched against our ad-hoc state management. When that was removed, if nothing triggered a dirty event, a render would never be triggered.Fix: Always render the first frame. Bring back a limited version of
needsRender
in the form ofisFirstRender