Hi, I've been playing with the pick infrastructure in 0.90 and find that it doesn't meet my needs. The issue is that events from all artists go to the same callback, so you are forced write your callback as a series of if statements for each artist which may receive a pick event.
I would rather have an infrastructure more like a canvas, where I can register callbacks to particular handles for particular mouse events (enter, leave, motion, press and release). I would like to rely on the zorder attribute of artists when processing the events. If the callback succeeds, then the event is consumed and no more handles are checked. If the callback fails then the next lower zorder handle is checked. I can simulate what I want with the current infrastructure by having the mouse events call figure.pick() and the pick event capture every object that was picked, but it is ugly and not very efficient (not every object wants to track enter/motion/leave events for example, but they get asked on every pick even if they only want to monitor mouse clicks). Instead I would like to start by splitting the current pick method into two parts: contains(event,picker) which returns truth value,details pick(event) which generates the current pick event Later I can construct the infrastructure I want on the contains() function for each artist. Does this approach seem reasonable to those who will approve the patches I will send? Thanks, Paul Kienzle [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
