-
-
Notifications
You must be signed in to change notification settings - Fork 18
Update Canvas usage #319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
HalfWhitt
wants to merge
3
commits into
beeware:main
Choose a base branch
from
HalfWhitt:update-canvas
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update Canvas usage #319
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Canvas usage (and some Color usage) has been updated to reflect changes in Toga's API. |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this indicate the need for a
self.canvas.clear()(orself.canvas.root_state.clear()?) method? While this is legal, it seems like a common enough use case that it might warrant an entry point.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair... it's just a little odd in terms of comparing it to the HTML API. Since Context2d doesn't give any direct access to the "history" of drawing actions, there's no way to explicitly tell it to discard prior drawing operations. As far as I'm aware, the standard way to erase the whole canvas is by calling
clearRectand telling it the entire canvas as the rectangle. We don't have aclear_rectmethod yet, but once we do, that would presumably just be one more drawing operation added to the list. The effect would be the same... except that, of course, you could always delete theClearRectaction later, and everything should still be there.Add to that the fact that, at least as far as things are currently implemented, Canvas already inherits
clear()from Widget. Granted, it just throws an error, and I don't think there's any risk Canvas will ever need to have children, so we could give it is own customclear()method that handles this. But Barbara Liskov might send someone to break our kneecaps.So... yes, I do think it's a common use case, and a good button to expose. I'm just not positive of the best way to spell it, in betwixt our various idioms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, the ironies... Now I remember: that the existence of
clear()on the base Widget was the reason we moved all the drawing instructions tocanvas.context...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The good news is that since
clearisn't part of the HTML API, we're not married to that name for such a method. (Although because it is a natural guess, we could overwriteWidget.clearjust to add a more helpful error message that says what to use instead.)