-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Errorbar layering #409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does anyone know a workaround? I plot a lot of lines and afterwards I want to plot the error bars on top of them. This works for the upper and lower horizontal lines, but the vertical line is in the back. |
Ok, I found the solution already. I plot all those lines which should appear in the background with the keyword zorder=1. That one did the trick. |
@WeatherGod Is this fixed? Sorry to pester you. |
Nudge. |
note to self: set a default zorder for error bars |
This is actually a deeper issue than I first grasped. Because Short of re-writing how This is another case where having sematic high-level containers (see thread on mailing list about the D3 work) would be helpful. |
Removed the milestone and flagged and taagging as wontfix. To get the ordering correct, you need to explicitly set the z-order of each @WeatherGod If you agree, please close. |
I agree that it would be hard to fix this problem. This is yet another reason for updating our rendering engine to utilize a DOM tree traversal rather than this layering approach. Maybe we should have a new tag "cantfix"? |
done |
This was first reported on the mailing list by me here: http://old.nabble.com/errorbar-layering-issue--td32149181.html
An image depicting the problem is also available through that link. The message text is below.
I have come across an odd layering issue with errorbars. The errorbar caps are not drawn at the same layer as the errorbar itself. Also, the line connecting multiple errorbars are plotted on a completely different layer than the errorbars. I am attaching an example demonstrating this. Note the green caps are showing up on top of the red errorbar, meanwhile, the red errorbar is drawn on top of the green errorbar. Also notice that the thin red line connecting the red errorbars is showing up on top of the green cap for lambda = 1.
I am not exactly sure how this should be fixed. It is most likely an issue with the fact that the caps are drawn as markers instead of a line (I am guessing so that the marker would then be sized based on width in points instead of data). When an axes' child objects are z-sorted, the objects that do not declare a z-order are loaded in the order of their creation (or is it in some arbitrary order based on the type of collection?).
The text was updated successfully, but these errors were encountered: