fix set logical size in JupyterRenderCanvas#50
Merged
almarklein merged 1 commit intopygfx:mainfrom Dec 31, 2024
kushalkolar:main
Merged
fix set logical size in JupyterRenderCanvas#50almarklein merged 1 commit intopygfx:mainfrom kushalkolar:main
JupyterRenderCanvas#50almarklein merged 1 commit intopygfx:mainfrom
kushalkolar:main
Conversation
Member
|
Yeah I think this makes sense! Thanks! |
Contributor
Author
|
Thanks! I can also confirm that our tests work again after this change, can we get a bugfix release with this so our CI works again 😄 |
This file contains hidden or 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
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 initial logical size for
JupyterRenderCanvasis (0, 0) by default which causes sporadic divide by zero errors with WGPU validation and also creates issues for CI sinceget_frame()returns blank screenshots and then improperly sized screenshots before returning correct screenshots (I'm guessing until it processes events to resize the canvas?). This changes it so that if a size is specified for the canvas in the constructor, then that size is used for the logical_size in addition to the css width and height. Not sure if we should just change the default size in the constructor from (0, 0) as well.