matplotlib-devel Mailing List for matplotlib

On 2015年05月06日 9:19 AM, Federico Ariza wrote:
> Hello
>
> Is there any reason why the "num" property is assigned to the manager
> and not to the figure?
I think this is because the figure is at the object-oriented API level. 
 The manager is in the pyplot state-machine level.
> Pyplot.gcf is to get the "current figure" not the "current manager".
It is really "get current managed figure", combined with the original 
idea that the manager is the pyplot layer on top of the figure, with one 
manager per figure. The "current" concept comes from the state machine.
>
> In general this is not a problem. But I'm working on MEP23 where one
> manager can contain several figures. And it would be pretty nice if I
> could reference the figures by that number not the managers.
>
> A priori, do you see any problem with a PR changing that?
It seems like it could work--but what will it do to existing user code?
Eric
>
> Thanks
> Federico
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hello
Is there any reason why the "num" property is assigned to the manager and
not to the figure?
Pyplot.gcf is to get the "current figure" not the "current manager".
In general this is not a problem. But I'm working on MEP23 where one
manager can contain several figures. And it would be pretty nice if I could
reference the figures by that number not the managers.
A priori, do you see any problem with a PR changing that?
Thanks
Federico