Eric Firing wrote:
John,
I made some more changes in quiver, and I think they will ensure that
dpi changes are handled correctly as far as arrows are concerned, both
in the plot and in the key.
There is still a problem with the key label, and it can be seen clearly
in the attached slight modification of quiver_demo.py. There are
actually two visible problems:
1) The hline generated by frac is too long with dpi=50.
2) The positioning and sizing of the key bbox are also dpi-dependent, as
I verified by using your bbox-display trick.
The plot thickens. The postscript backend is completely confused by the
quiver plot. Try the attached example.
pdf seems OK.
Eric
import sys
import matplotlib
matplotlib.use('ps')
from pylab import *
X,Y = meshgrid( arange(0,2*pi,.2),arange(0,2*pi,.2) )
U = cos(X)
V = sin(Y)
#1
figure()
Q = quiver( U, V)
qk = quiverkey(Q, 0.5, 0.92, 2, r'$2 \frac{m}{s}$', labelpos='W',
fontproperties={'weight': 'bold'})
l,r,b,t = axis()
dx, dy = r-l, t-b
axis([l-0.05*dx, r+0.05*dx, b-0.05*dy, t+0.05*dy])
title('Minimal arguments, no kwargs')
savefig('q1_defdpi.eps')
savefig('q1_050.eps', dpi=50)
savefig('q1_150.eps', dpi=150)
savefig('q1_072.eps', dpi=72)
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
