On Tue, Feb 28, 2012 at 10:44 AM, Benjamin Root <ben.r...@ou.edu> wrote:
>
> The Lasso disconnects itself after the button_release event because that's
> what indicates that you are done. The user gets back a single Line2D
> object that is assumed to represent a single path with no breaks. Reusing
> the Lasso widget would be a situation that would require a different idiom
> for user interaction. I wouldn't be against a "MultiLasso" widget that
> works differently from Lasso, but I really wouldn't want to make changes to
> existing user widgets. It is iffy enough about whether to remove the
> point-count-check.
>
>
I added the point count check according to git blame and I don't remember
why but I agree is doesn't look like it makes sense to me. I think this
lasso is lightly used based on the volume of questions we get about it.
One reason it may be lightly used is because it is hard to work with. If
we can improve it, even changing functionality, I would be in favor. Eg,
allowing the same Lasso to handle repeated selections makes sense to me.
If the change looks too onerous, we could call it Lasso2 and deprecate the
former.
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
