From: Pål G. E. <pa...@gm...> - 2012-02-06 17:15:29
|
Hi That was a very nice explanation of how autoscale works, thank you very much :D After now understanding how the function autoscale function works, I see that this would be a major change in the code, as it would require the axes to know all of the bounding boxes, and not only one of them. As it, at least in my code, is easy to calculate the new limits on the unset axis, I would not put this up as something that should be a feature. Though I think the documentation for autoscale, section axis could be a bit clearer and state that autoscaling only one axis autoscales that axis with respect to everything plotted, even though xlim/ylim has been set. Regards Pål On 6 February 2012 18:02, Benjamin Root <ben...@ou...> wrote: > > > On Mon, Feb 6, 2012 at 4:47 AM, Pål Gunnar Ellingsen <pa...@gm...>wrote: > >> Hi >> >> I understand that it would be hard to implement, as it requires that all >> the points are checked, which for a arbitrary plot is not easy. >> Though is this not what is already done for the normal autoscale, or have >> I misunderstood how the normal autoscale is done? >> >> I would like to have this as a new feature, as it would prove useful for >> analysing graphs, especially in scientific research. >> >> Kind regards >> >> Pål >> >> >> > Pal, > > Normal autoscaling (when aspect is None, which is default) means to > display all the data that has been plotted. This is possible because the > plotting functions (which were given the data as input) updates the limits > of the "known data bounding box" for the axes. This data is not stored > except within each artist object, in their own form. It becomes difficult > to then "re-query" that data in the general case. It isn't to say that it > isn't possible to do, just that the architecture isn't set up to query > subsets of collections. > > I hope this is clearer, > Ben Root > > |