plotting

As a follow-up to #11540, we would like to add metadata to as many examples as possible. This will not only make the examples more usable as they are right now, but it will also open up new possibilities to search for and crosslink examples.

For the purpose of this issue, 'standalone examples' are all .py files in these folders in this repository:

• examples/plotting/file
• `examples/mode

Bug summary

Currently, when the mouseover coordinates/value text has two lines (typically when hovering over an imshow()):

• qt right aligns the text
• tk center aligns the text
• gtk and wx left aligns the text
• (I haven't checked for macos and jupyter)

Given that the text is shown at the right edge of the toolbar, I think right aligning looks better? This is probably just a matte

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

https://readthedocs.org/projects/chartify/builds/

It is currently a pain to use an OxyPlot.WinfowsForms.PlotView with a transparent background: it throws if you set its BackColor to transparent. To avoid this, it is necessary to set the ControlStyles.SupportsTransparentBackColor style to true on the PlotView; however, Control.SetStyle is protected, so consumers must resort to reflection or extending PlotView to do so. This could be

I think it could be useful, when one wants to plot only e.g. class 1, to have an option to produce consistent plots for both plot_cumulative_gain and plot_roc

At the moment, instead, only plot_roc supports such option.

Thanks a lot

Annotations don't look good in a Heatmap with a large amount of data and those that are rendered in the high values range are barely visible with the default color map. Heatmaps generated with the Bokeh backend don't have annotations by default.

See this example taken from the reference gallery:
![image](https://user-images.githubusercontent.com/35924738/140487561-3cdb38ea-8694-4328-ab9f-bfdda

What is the feature ?

I'm trying out this library for the first time and there's some places where it would be delightful to have shorthand functions:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. Currently, lots of boilerplate is required for e.g. white-on-black plotos
   • a cool start would b

I don't think this is a duplicate ticket, even though it's quite an obvious feature after that cat demo at SciPy2018.

The code that selects and renders the different geos is here in the THREE.js code
https://github.com/maartenbreddels/ipyvolume/blob/master/js/src/scatter.js#L57

I don't know quite where/how to inject the mesh definition compatible with the data file of this form, but i

It would be nice to support adding arrow annotations to plots, similar to pyplot.arrow (from #245).

From here: http://makie.juliaplots.org/stable/plotting_functions/heatmap.html#MakieCore.heatmap there is really no info, e.g. how to choose colormap, how to set color range.

About 50% of our docstrings in PyVista have examples. This is fairly good, especially considering that many of these objects are not publicly exposed.

However, for modules like pyvista.plotting.plotting, it would be great to see nearly 100% coverage considering how important it is to be able to demonstrate the individual methods of the Plotting class.

This is a great first issue since it

As noted in this Stack Overflow question it would be good to be clear what’s going on in this function, including the equation.