Axis default zorder

[kcrisman]

There was a recent "report a bug" report on zorder not working for
the Disk class. I have fixed this, but discovered something else when
one fixes this:

sage: d3 = disk((0,0), 0.5, (0, 2*pi), color = 'green', zorder= 2)
sage: d4 = disk((0,0), 0.25, (0, 2*pi), color = 'yellow', zorder=3)
sage: d3 # disk lets you see the axes
sage: d4 # disk doesn't let you see the axes

What is the default zorder for the axes, and should it be changed -
that is, should the axes *always* be visible, sometimes, never... or
is there some convention on this sort of thing? In any case, we might
want to document it if there is something obvious.

Also, the default zorder for polygons is 1, but for everything else
for which it exists seems to be 0. Is that bad?

- kcrisman

[kcrisman]

On Dec 29, 10:27 pm, kcrisman <kcris...@gmail.com> wrote:
> There was a recent "report a bug" report  on zorder not working for
> the Disk class. I have fixed this, but discovered something else when

Trac #7793

> one fixes this:
>
> sage: d3 = disk((0,0), 0.5, (0, 2*pi), color = 'green', zorder= 2)
> sage: d4 = disk((0,0), 0.25, (0, 2*pi), color = 'yellow', zorder=3)
> sage: d3 # disk lets you see the axes
> sage: d4 # disk doesn't let you see the axes
>
> What is the default zorder for the axes, and should it be changed -
> that is, should the axes *always* be visible, sometimes, never... or
> is there some convention on this sort of thing?  In any case, we might
> want to document it if there is something obvious.
>
> Also, the default zorder for polygons is 1, but for everything else

And arrows are 2. There is also a little inconsistency in how
defaults for this are arranged - sometimes via @options for the
lowercase, which would lead to a KeyError if one used the Uppercase
version directly for some reason. I don't know whether to consider
these bugs, though.

- kcrisman