A little more investigation here shows that a component named 'valid
box' is created sometimes. I will try and figure out exactly what is
going on and see if I can document it and maybe no functionality
changes are needed.
David
ShowBox realizes the box that is the calculated bounding box and
makes a call to DXBoundingBox but doesn't change the field itself.
Maybe a better way to solve it would be to add an attribute that
would affect which way the bounding box function is called on an
object. We could set it the way it is now as default, (no
attribute--ignore invalids) but allow for the option to not ignore
the invalids. It would mean adding an extra step of looking up the
attribute and making the decision every-time the DXBoundingBox
function is called.
What do you think,
David
There are cases in which you may be subsetting a field by filtering on
data, positions, etc. marking elements as invalid or you may have imported
data that way. The invalid may be time varying, but the bounding box is
not. Thus, you can have a consistent volume or area even as data within it
are changing.
Of course, not everyone will need such flexibility. Perhaps adding a
validity option to ShowBox similar to that of ShowBoundary would suffice.
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
