Set minimum size of MatDataPlot#56
Open
floesche wants to merge 1 commit intoros-visualization:crystal-develfrom
Open
Set minimum size of MatDataPlot#56floesche wants to merge 1 commit intoros-visualization:crystal-develfrom
floesche wants to merge 1 commit intoros-visualization:crystal-develfrom
Conversation
When the size of MatDataPlot gets down or below the minimum size of the QVBoxLayout it contains, the matplot backend fails as it requires a positive size. Explicitely setting the minimumSize of MatDataPlot seems to fix this problem.
This was referenced Feb 4, 2021
Merged
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
1 participant
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.
When the size of MatDataPlot gets down or below the minimum size of the
QVBoxLayout it contains, the matplot backend fails as it requires a
positive size. The error message is shown in #54.
Explicitly setting the minimumSize of MatDataPlot bigger than the size of the Layout it contains seems
to fix this problem.