bnwylie at sandia.gov
Tue Feb 1 09:54:39 EST 2005
I find the label logic in vtkCubeAxesActor2D to be REALLY silly. It
doesn't actually give the real bounds of the object it gives something
There are several issues
1) The corner offsets are most likely meant to 'uncrowd' the text. This
is fine but then the values of the bounds are actually changed to
reflect the offsets. This can be REALLY deceiving. Your dataset has
geometric bounds from 0 to 50 and the labels say 0.05 to 49.5 ... Arg!
2) The clipbounds function is clever but also really irritating. When
you have the dataset almost fill the screen (which is almost always) the
end 'wiggle' around. Even though the ends aren't actually off the screen
the value 'wiggles'.
I was with a user yesterday and I cannot tell you how frustrating it was
to explain why he could never actually see the real bounds of his
I would like to add an iVar (something like ShowRealBounds) that is
defaulted to ON. It will add a small amount of logic that would show the
real bounds (even with corneroffsets) and would not 'clip' the axes.
Also I'm finding that corneroffset should probably be 0.1. This seems to
uncrowd the text a bit better.
I would like to make these changes this morning. So that we can hit the
continuous builds. Please let me know if you would like me to not do so.
Sandia National Laboratories
MS 0822 - Org 9227 - Building 880/A1-J
(505) 844-2238 FAX (505) 845-0833
More information about the vtk-developers