Hello,
I am working with the Line3D objects in the mplot3d toolkit. I have noticed
that the .set_data() function is not overloaded from the Line class,
therefore, there is no direct way to set the line data. Should a
.set_data() function be created for Line3D or is there some inherent barrier
to
Along the same vein, I have noticed that the Axes3D object does not have a
.set_zlim() function, instead opting to use .set_zlim3d(). The same is true
with xlim() and ylim(), implementing a different function for .set_xlim3d()
than the inherited .set_xlim(). Is this intended?
Thanks,
Ben Root
O
Hi,
I've been debugging this for hours now and could really use the help
of someone smarter than me. In working on blitting with animations,
I've run into a problem when trying to use blitting + multiple
subplots + lines with markers. It's an esoteric combination to be
sure, but I have a script (a
Alright, before I go to bed, I found the following line in
src/_backend_agg.cpp at line 709 (in draw_markers()) makes all the
difference:
set_clipbox(gc.cliprect, rendererBase);
Commenting out this line fixes my problem. I'm not sure why it's a
problem, (maybe a missing restore to previous state
Hello all,
I have always been a bit troubled with how Axes3D object is a bit of a
2nd-class citizen in matplotlib. In particular, it is very common to create
a new axes using .add_subplot() or .gca(), but you can't do that with
Axes3D. You also can't create subplots of 3d figures, you have to cr
