John Hunter wrote:
> On Sun, Apr 27, 2008 at 12:56 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> The plot thickens. The postscript backend is completely confused by the
>> quiver plot. Try the attached example.
>
>
> Argg, that was a subtle one -- there was a bug in backend ps which was
> e
On Sun, Apr 27, 2008 at 8:28 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> Argg, that was a subtle one -- there was a bug in backend ps which was
> exposed only if you are using a path collection with offsets,
> transoffset and clippath and cliprect both None. In that scenario,
> the translat
On Sun, Apr 27, 2008 at 12:56 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> The plot thickens. The postscript backend is completely confused by the
> quiver plot. Try the attached example.
Argg, that was a subtle one -- there was a bug in backend ps which was
exposed only if you are using a pa
On Sun, Apr 27, 2008 at 3:14 AM, Eric Firing <[EMAIL PROTECTED]> wrote:
> 1) The hline generated by frac is too long with dpi=50.
The problem with the hline appears to be that the width of the line in
the frac has a component that depends on the thickness
thickness = state.font_output.get_u
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 m
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 quive
