[vtkusers] oblique vtkImageData bounds

[Jason Crane]

Hi, 

Can someone advise me about the proper way to handle initializing a vtkImageData object from an oblique acquisition?  In particular, if a vtkImageData object's dimensions, spacing and origin are initialized in world coordinates, the object's computed bounds aren't necessarily correct in world coordinates if the data corresponds to an oblique acquisition.  If the method that computes the bounds is overridden to account for the acquisition orientation (direction cosines) would that be problematic for vtkAlgorithms that operate on vtkImageData such as vtiImageReslice or others?

Thank you,
Jason