Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faster implementation of draw_rubberband in GTK+ backend #224

Closed
ddale opened this issue Jun 20, 2011 · 2 comments
Closed

Faster implementation of draw_rubberband in GTK+ backend #224

ddale opened this issue Jun 20, 2011 · 2 comments

Comments

@ddale
Copy link
Contributor

ddale commented Jun 20, 2011

Original report at SourceForge, opened Sun Jun 27 05:52:00 2010

Hi! I've experienced a problem while embedding plotting canvas in my application. During selecting zoom area the plot area was incorrectly repainted (shifted upwards). It seems that screen copy coordinates incorrectly computed in some cases. Ive made simple implementation, which do not require to copy screen at all. In my case it works correctly and, seems. much faster.

The same can be done for other dynamical widgets.

Attached patch made against matplolib version 0.99.3.

Sincerely, Evgeny

SourceForge Comments

On Tue Jun 29 18:35:45 2010, eugeneai wrote:

Do not activate both cross-hair widget and rubber band for zooming.

On Sun Jun 27 12:56:11 2010, eugeneai wrote:

My patch is incompatible with widgets, like cross-hair, based on blits. They should be also renewed.

SourceForge History

  • On Sun Jun 27 05:52:00 2010, by eugeneai: File Added: 378509: backend_gtk.py.diff
@pelson
Copy link
Member

pelson commented Sep 2, 2012

@eugeneai : I believe this was your original issue. You don't happen to have the diff do you? Would you be willing to submit it as a pull request if so? (if not, just posting it here would be helpful)

Unfortunately, without further information from @eugeneai we will have to close this issue (the sourceforce migration lost some of this information).

@tacaswell
Copy link
Member

This was last triaged a year ago, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants