Lazily initialize static bitmaps. #2543
Closed
Conversation
This file contains 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
I/O is forbidden in web workers, so creating a bitmap causes an error. One solution is to put off creating the bitmaps until they're used, which they typically aren't in a web worker.
|
I took another look and found a better place to handle this: openfl/lime@166ac06. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 web workers coming up in Lime 8.2.0 create a new static context on the background thread, initializing all static variables. Problem is, web workers aren't allowed to do I/O, so creating a bitmap causes an error. One solution is to lazily initialize these particular bitmaps.
All of OpenFL's other static variables work fine, as far as I'm aware.