Chris,
Examining the MovingElements.py program you use the obj.GetOutlinePoints()
method to return the position of the box. I tried this instead of
obj.CalcBoundingBox(), but the result was the same, the returned values
froze.
Clearly this works with Navcanvas in the MovingElements.py demo. So it has
to be how the zoom is being invoked through Floatcanvas on it’s own.
It’s as if I am not referencing the correct instance of the object. I need
to dig a little deeper here.
FYI – The floatcanvas zoom call I am using is ….
def OnMouseWheel(self,event):
zratio = 1 + 1.0*event.m_wheelRotation / 1200
self.Canvas.Zoom(zratio)
David
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of David Poundall
Sent: 22 December 2007 13:15
To: 'Mailing List for the wxPython Float Canvas.'
Subject: [fc] Bounding Box calculation locking up.
Chris,
Using Floatcanvas.py revision 51. After a move and a zoom I am finding that
the moved objects bounding box calculation (rectangle shape) locks up. No
matter where I move the object to after the zoom, the bounding box
calculation always returns the pre-zoom, post move calculated result.
This is operating without NavCanvas.
If you see this effect with Navcanvas, can you determine if we have a bug or
a feature here?
If it works OK for you with Navcanvas please ping me back and I will
assemble a demo app so that you can see the effect directly.
Cheers
David
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.17.5/1190 - Release Date: 19/12/2007
19:37
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.17.5/1190 - Release Date: 19/12/2007
19:37
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.17.5/1190 - Release Date: 19/12/2007
19:37
_______________________________________________
FloatCanvas mailing list
[email protected]
http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas
