ENH: errorbar in qt figureoptions #18650
Draft
+38
−3
Conversation
Possibly the most controversial change is adding a generator to flatten a nested sequence, I added this to make it easier to grab all the lines out of |
There is a |
I'll remove the flatten I added, and use the other one. Otherwise is the PR in a suitable form? |
@QuLogic refactored to use |
QuLogic
reviewed
Oct 16, 2020
Who is our figureoption guru? I've never used it, but hopefully someone will step up and shepherd this. |
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.
PR Summary
I'd like to change various properties of an errorplot using a Qt figureoptions dialogue. This dialog is presented when NavToolBar is created. At the moment
errorplot
s do not show up in the Curves tab, so one can't change their colour, markersize, etc.This PR detects if an ErrorbarCollection is present, and adds it to the Curves popup list. This permits adjustment of the line/marker properties of the 'host' Line. Pragmatically the bars/caps of the
errorplot
are set to be the same color as the host Line, and the same linewidth of the host Line.fixes #18631
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
andpydocstyle<4
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).The text was updated successfully, but these errors were encountered: