The second example on http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to expose a bug, which is clearly visible in the vector version: The blue curve with zorder=2 is plotted below the frame and all others with zorder >= 3 are plotted above the frame. This is because the frame zorder is hardcoded to be 2.5. This behaviour is certainly unexpected by most users. How can one modify the mutual zorder of lines without conflicting with standard axis elements? -- View this message in context: http://matplotlib.1069221.n5.nabble.com/bug-in-zorder-example-tp45342.html Sent from the matplotlib - users mailing list archive at Nabble.com.
you can always change the zorder of the frame using set_zorder(). Are you talking about the frame of the legend or the plotting area? On Mon, Apr 6, 2015 at 11:23 AM, plotter <pl...@tr...> wrote: > The second example on > http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to > expose a bug, which is clearly visible in the vector version: > > The blue curve with zorder=2 is plotted below the frame and all others with > zorder >= 3 are plotted above the frame. This is because the frame zorder > is > hardcoded to be 2.5. This behaviour is certainly unexpected by most users. > How can one modify the mutual zorder of lines without conflicting with > standard axis elements? > > > > -- > View this message in context: > http://matplotlib.1069221.n5.nabble.com/bug-in-zorder-example-tp45342.html > Sent from the matplotlib - users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > 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-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
zorder can be negative, if you want to ensure that all of your lines are always below all of the standard axis components simple decrease the zorder of the elements you want behind rather than increasing the zorder of the elements you want in front. @ben look at the top left of http://matplotlib.org/mpl_examples/pylab_examples/zorder_demo_01.hires.png and compare where it looks like the red and green lines are clipped. Tom On Thu, May 7, 2015 at 11:14 AM plotter <pl...@tr...> wrote: > The second example on > http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to > expose a bug, which is clearly visible in the vector version: > > The blue curve with zorder=2 is plotted below the frame and all others with > zorder >= 3 are plotted above the frame. This is because the frame zorder > is > hardcoded to be 2.5. This behaviour is certainly unexpected by most users. > How can one modify the mutual zorder of lines without conflicting with > standard axis elements? > > > > -- > View this message in context: > http://matplotlib.1069221.n5.nabble.com/bug-in-zorder-example-tp45342.html > Sent from the matplotlib - users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > 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-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
But, why is it doing that only along the top edge and not the other edges (or are my eyes that bad)? On Thu, May 7, 2015 at 11:30 AM, Thomas Caswell <tca...@gm...> wrote: > zorder can be negative, if you want to ensure that all of your lines are > always below all of the standard axis components simple decrease the > zorder of the elements you want behind rather than increasing the zorder of > the elements you want in front. > > @ben look at the top left of > http://matplotlib.org/mpl_examples/pylab_examples/zorder_demo_01.hires.png > and compare where it looks like the red and green lines are clipped. > > Tom > > On Thu, May 7, 2015 at 11:14 AM plotter <pl...@tr...> wrote: > >> The second example on >> http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to >> expose a bug, which is clearly visible in the vector version: >> >> The blue curve with zorder=2 is plotted below the frame and all others >> with >> zorder >= 3 are plotted above the frame. This is because the frame zorder >> is >> hardcoded to be 2.5. This behaviour is certainly unexpected by most users. >> How can one modify the mutual zorder of lines without conflicting with >> standard axis elements? >> >> >> >> -- >> View this message in context: >> http://matplotlib.1069221.n5.nabble.com/bug-in-zorder-example-tp45342.html >> Sent from the matplotlib - users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> 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-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> > > > ------------------------------------------------------------------------------ > 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-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > >
It is doing it every where. Also look at the tick above the 2 on the bottom it is slightly clipped. It is definitely seems worse on the top, which might be showing a fence-post issue in the clipping/Agg rendering. As the OP points out zooming in on http://matplotlib.org/mpl_examples/pylab_examples/zorder_demo_01.pdf makes it really obvious that this is the case everywhere. That said, I don't think that this is a 'bug' persay. We have to pick _some_ zorder for the frame and 2.5 is is good as any other. We do have a documentation problem as I don't know where that information is other than in the source. Tom On Thu, May 7, 2015 at 11:38 AM Benjamin Root <ben...@ou...> wrote: > But, why is it doing that only along the top edge and not the other edges > (or are my eyes that bad)? > > On Thu, May 7, 2015 at 11:30 AM, Thomas Caswell <tca...@gm...> > wrote: > >> zorder can be negative, if you want to ensure that all of your lines are >> always below all of the standard axis components simple decrease the >> zorder of the elements you want behind rather than increasing the zorder of >> the elements you want in front. >> >> @ben look at the top left of >> http://matplotlib.org/mpl_examples/pylab_examples/zorder_demo_01.hires.png >> and compare where it looks like the red and green lines are clipped. >> >> Tom >> >> On Thu, May 7, 2015 at 11:14 AM plotter <pl...@tr...> wrote: >> >>> The second example on >>> http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to >>> expose a bug, which is clearly visible in the vector version: >>> >>> The blue curve with zorder=2 is plotted below the frame and all others >>> with >>> zorder >= 3 are plotted above the frame. This is because the frame >>> zorder is >>> hardcoded to be 2.5. This behaviour is certainly unexpected by most >>> users. >>> How can one modify the mutual zorder of lines without conflicting with >>> standard axis elements? >>> >>> >>> >>> -- >>> View this message in context: >>> http://matplotlib.1069221.n5.nabble.com/bug-in-zorder-example-tp45342.html >>> Sent from the matplotlib - users mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> 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-users mailing list >>> Mat...@li... >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >>> >> >> >> ------------------------------------------------------------------------------ >> 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-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> >> >
