You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Drawing rubberband box outside of view crash backend_macosx #201
Drawing a large rubberband box causes backend_macosx to crash in draw_rubberband with the error,
Original exception was:
Traceback (most recent call last):
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/backend_bases.py", line 1625, in motion_notify_event
self.callbacks.process(s, event)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/cbook.py", line 265, in process
proxy(_args, *_kwargs)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/cbook.py", line 191, in call
return mtd(_args, *_kwargs)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/backend_bases.py", line 2573, in drag_zoom
self.draw_rubberband(event, x, y, lastx, lasty)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/backends/backend_macosx.py", line 420, in draw_rubberband
self.canvas.set_rubberband(x0, y0, x1, y1)
TypeError: integer argument expected, got float
ipython's stack trace claims draw_rubberband was called with,
I was able to replicate this bug with older versions of matplotlib but not with the current git master. Can you still trigger this bug with the current git master? If not, I suggest we close this issue.
Activity
mdehoon commentedon Aug 21, 2011
I was able to replicate this bug with older versions of matplotlib but not with the current git master. Can you still trigger this bug with the current git master? If not, I suggest we close this issue.
jdh2358 commentedon Mar 17, 2012
Darren, @mdehoon commented in this pull request
#741
that this issue should be closed -- are you able to confirm?
mdehoon commentedon Dec 12, 2012
I still cannot replicate this bug. Let's wait another week, and close this issue if there are no further reports of this bug.
pelson commentedon Dec 12, 2012
Yes agreed. Lets close this until we have an actual user who is reporting it.