Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Make FigureManagerWx more consistent with other backends.#13153
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
window : wxFrame | ||
a wxFrame instance - wxpython.org/Phoenix/docs/html/Frame.html |
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 link is broken and if anything the only link should be to the wxpython general docs at the top of the module (perhaps).
7e54812
to0986dad
CompareBecause wx expects (AFAIU) parent widgets to be fully set up before children, I don't think it is possible to match the model of other backends where we first create the Canvas and then let the Manager create the toplevel window that hosts it :/ |
Uh oh!
There was an error while loading.Please reload this page.
PR Summary
Builds on top of#13146 to avoid a rebase.Note that unlike in#10606, FigureManagerWx is a pure-python class, not a wx Widget, so there's no problems with wxness of the constructor there.
PR Checklist