Repository navigation
fix bug #3690: don't call evt.Skip() when window has just been destroyed - #10415
Merged
tacaswell merged 1 commit intoFeb 11, 2018
Merged
Conversation
Member
|
Thanks @DietmarSchwertberger ! |
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.
PR Summary
Fixes #3690
Forwarding the event to a destroyed window caused the crash.
It would be best not to call
evt.Skip()at all if a key was handled byFigureCanvasBase.key_press_event()but that's probably more difficult to implement.PR Checklist