GNOME Bugzilla – Bug 591478
Surface plots should allow multiple series
Last modified: 2018-05-22 13:02:44 UTC
If 2 surface plots are included in teh same chart, the first one is drawn and then the second one without regard to which surface is closer to the view point. I will be attaching a file showing two charts that only differ in the order of the surface plots. In the right chart the lower surface hides the upper surface.
Created attachment 140472 [details] sample file
I know. Searching for intersections in 3d is not implemented and will probably not be there in any foreseable future. That's why 3D plots support only one series and why they need the x and y data to be ordered. I suppose it is possible to limit charts to only one 3D plot.
One can get a much better result even without calculating intersections. Even ust plotting the faces in distance ordering will greatly improve hte image since only the faces along the intersection line may be wrong. In the charts of the sample file, the image would be correct since those surfacces do not intersect.
This would need to delegate the rendering to the chart instead of the plot. This seems feasable, but not trivial. It would probably mean that we store a cairo_surface_t for each tile, or only one surface for the plot, but use a clip region for the tile. Anyway, we would need a new API. I think it is better to improve what we have using only one plot and one series in the chart (there are many details which were not addressed), then we might think to play with surface intersections.
Done. Andreas, either we close this bug or change its title to "Allow surfaces crossing" or so and set priority to enhancement.
OKay, disallow having several surface plots of course fixes this bug but of course having several surface plots or a surface plot plus a contour plot would be very useful!
I'll investigate when time permits (may be next summer). Contour plots also need a lot of love.
Fixed.
not fixed at all, wrong bug
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/goffice/issues/17.