That sounds fine to me. I just wanted to make sure that I wasn't glossing over
a bug that could turn up elsewhere.
Thanks,
Darren
On Monday 10 March 2008 08:46:36 am Michael Droettboom wrote:
> No, I didn't see this message, but I think we arrived at the same
> conclusion. I think the solution
No, I didn't see this message, but I think we arrived at the same
conclusion. I think the solution is just to calculate the width and
height in the same way in both places (copy_to_bbox and the Qt blitting
code in Python). We can't change bbox.bounds, since many other parts of
the code rely o
Sorry, I didn't see this latest e-mail before I replied before. I see
the shearing now that I've adjusted window size. Maybe it could be
related to the fact that width != span? Anyway, I'll investigated
further and get back.
Cheers,
Mike
Darren Dale wrote:
> On Friday 07 March 2008 4:58:03
With the qt4agg backend, I also get no cursor with "useblit=False", but
when "useblit=True" it seems to work just fine -- I don't see any
shearing. By shearing I assume you mean the image is warped like a
parallelogram? Or do mean tearing, in that it isn't updating fast
enough? (FWIW, I don'
On Friday 07 March 2008 4:58:03 pm Darren Dale wrote:
> I am having some trouble with the Cursor widget with the qt4agg backend.
> Here is a short script which works with the gtkagg backend with useblit
> either true or false:
>
> --
> from matplotlib import rcParams
> rcParams['backend']='
I am having some trouble with the Cursor widget with the qt4agg backend. Here
is a short script which works with the gtkagg backend with useblit either
true or false:
--
from matplotlib import rcParams
rcParams['backend']='gtkagg'
from pylab import *
from matplotlib.widgets import Cursor
