| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| `.Colormap.set_extremes` and `.Colormap.with_extremes` | ||
| `````````````````````````````````````````````````````` | ||
|
|
||
| Because the `.Colormap.set_bad`, `.Colormap.set_under` and `.Colormap.set_over` | ||
| methods modify the colormap in place, the user must be careful to first make a | ||
| copy of the colormap if setting the extreme colors e.g. for a builtin colormap. | ||
|
|
||
| The new ``Colormap.with_extremes(bad=..., under=..., over=...)`` can be used to | ||
| first copy the colormap and set the extreme colors on that copy. | ||
|
|
||
| The new `.Colormap.set_extremes` method is provided for API symmetry with | ||
| `.Colormap.with_extremes`, but note that it suffers from the same issue as the | ||
| earlier individual setters. | ||
| Back | FazBrowse Home | New Git URL |
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.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityI think we've decided not to put links in section titles for aestethic reasons.
But I'm going to merge as is. I'll anyway do a small colormap-related cleanup PR and will update there. While that's a bit of a messy way of working it saves us an extra review roundtrip here.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.