On Sat, Oct 23, 2010 at 7:09 AM, Kynn Jones wrote:
> Without knowing much about the internals of matplotlib, it seems to me that
> the best way to do this would be to define a container class that can have
> itself as one of the contained elements. In this way, a containment
> hierarchy of arbitr
--- On Sun, 10/24/10, Ryan May wrote:
> > One solution is to add an .animation attribute to the
> > Figure class, which is None by default (for non-animated
> > drawing).
> I'm not completely wild about it, because it just feels
> wrong to put something specific to animation inside figure.
OK I s
On Fri, Oct 22, 2010 at 5:09 PM, Kynn Jones wrote:
> I need to generate a fairly complex chart, for which I need the ability to
> specify not only subplots, but also sub-subplots, and even
> sub-sub-sub-plots. (Our group has found such charts useful in the past, but
> they were generated using h
On Sun, Oct 24, 2010 at 10:35:03AM -0500, Ryan May wrote:
> On Sat, Oct 23, 2010 at 5:05 PM, David Carmean wrote:
[snip]
> > I've spent a few hours this weekend doing some meta-monkey-patching--
> > using __getattribute__ to decorate the setters on-the-fly to invoke
> > callbacks.process(*args)
[Putting this back on list after I mistakenly took it off.]
On Fri, Oct 22, 2010 at 11:45 PM, Michiel de Hoon wrote:
> Hi Ryan,
>
> Thanks for your reply.
>
> --- On Mon, 10/18/10, Ryan May wrote:
>> In the course of adding the animations, I also
>> added a "close_event" to the other backends, s
On Sat, Oct 23, 2010 at 5:05 PM, David Carmean wrote:
>
> As I blurted on -users, I'm thinking lately about callbacks in the
> non-GUI portions of the libraries--mostly Artist and subclasses.
> I'm curious if anybody else has been thinking about them?
>
> Ideally, I'd like to see the following:
>