matplotlib-devel Mailing List for matplotlib

I agree, while most of the time I call set_xlim() after all plotting is
finished, there are some cases where I call it before subsequent plot calls,
and this is a little nutty. I wonder how this change in behavior would
impact basemap which always seemed to have to code around this issue?
Ben Root
On Sun, Jun 27, 2010 at 7:39 PM, Paul Barrett <peb...@gm...> wrote:
> Seems like a reasonable request to me. When I use xlim to specify the
> axes in a plot session, I tend to use it multiple times. Therefore
> this default behaviour would seem reasonable.
>
> On Sun, Jun 27, 2010 at 4:40 PM, Eric Firing <ef...@ha...> wrote:
> > The present behavior of set_xlim and set_ylim can be surprising because
> > making the values stick for subsequent plotting in the same axes
> > requires manually calling set_autoscalex_on(False) etc. It would seem
> > more logical if set_xlim itself included the call to turn autoscalex
> > off--isn't that what a user would almost always want and expect?
> >
> > Rectifying this would constitute a significant change affecting some
> > existing user code.
> >
> > What are people's thoughts on this? Should the change made? If so, do
> > it abruptly, right now, as part of version 1.0? Or phase it in with a
> > temporary kwarg and/or rcparam? It would be nice to avoid all that
> > complexity, but may be we can't, except by leaving everything as it is
> now.
> >
> > Eric
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Seems like a reasonable request to me. When I use xlim to specify the
axes in a plot session, I tend to use it multiple times. Therefore
this default behaviour would seem reasonable.
On Sun, Jun 27, 2010 at 4:40 PM, Eric Firing <ef...@ha...> wrote:
> The present behavior of set_xlim and set_ylim can be surprising because
> making the values stick for subsequent plotting in the same axes
> requires manually calling set_autoscalex_on(False) etc. It would seem
> more logical if set_xlim itself included the call to turn autoscalex
> off--isn't that what a user would almost always want and expect?
>
> Rectifying this would constitute a significant change affecting some
> existing user code.
>
> What are people's thoughts on this? Should the change made? If so, do
> it abruptly, right now, as part of version 1.0? Or phase it in with a
> temporary kwarg and/or rcparam? It would be nice to avoid all that
> complexity, but may be we can't, except by leaving everything as it is now.
>
> Eric
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>