Eric Firing efir...@hawaii.edu writes:
John Hunter wrote:
One possibility would be to have a facecolor/edgecolor property on
the gc itself, which would be rgba tuples. Since the gc is almost
entirely internal, we can revamp it w/o affecting userland code,
though it would be nice to support
Jouni K. Seppänen wrote:
Eric Firing efir...@hawaii.edu writes:
John Hunter wrote:
One possibility would be to have a facecolor/edgecolor property on
the gc itself, which would be rgba tuples. Since the gc is almost
entirely internal, we can revamp it w/o affecting userland code,
Michael Droettboom wrote:
Jouni K. Seppänen wrote:
Eric Firing efir...@hawaii.edu writes:
John Hunter wrote:
One possibility would be to have a facecolor/edgecolor property on
the gc itself, which would be rgba tuples. Since the gc is almost
entirely internal, we can revamp it w/o
I don't quite like my solution but it seems to work.
It passes over the figure instance when initializing the
MixedRenderer, and let the renderer change the dpi of the figure when
changing the backend.
I hope some other developer who better understands the dpi thing take
a look and come up
Hi,
Does anyone know if there is a reason that quadmesh objects don't have a
method for setting the geometry of the grid (i.e. the _coordinates
attribute)? If there's not a reason, I'll add one.
Now, this gets to a larger scale matplotlib API question. Should I add this
as a property (either
