Graphics: Only check for threading issues once graphics is initialized #7455
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.
Maintainer merge checklist
Component: xxx
label.api-deprecation
orapi-break
label.release-highlight
label to be highlighted in release notes.versionadded
,versionchanged
as needed.This fixes an issue, where if you created graphics instructions before kivy gl thread was initialized (which seems to happen with ScrollView), it would the error that you're accessing the graphics from the wrong thread. This fixes so it only does it once the thread has been initialized.
While technically this would allow people to create graphics from another thread before the kivy thread was initialized and it wouldn't warn about it. But it shouldn't happen often and this would still warn for the most common situation, while not warning on false positive.