Hi there, Im guessing that images have the orientation of their axes specified in the header, which can be different from the global x,y,z axes. Surfaces and points dont. So, for example, an mitk::Surface contains a vtkPolyData, and all coordinates are in x,y,z coordinates. So, there is no other coordinate axes to chose from. Historically, mitk::PointSet used to just contain x,y,z coordinates but a while back, around 2015 I think, the file format itself was updated to include the orientation.
M > On 13 Jun 2018, at 14:45, Daniel Maleike <c...@maleike.de> wrote: > > Hi, > > I just noticed that the "Reinit" of Data Manager implements alignment to > object axes only in the special case of a single selected _image_. I > understand that for multiple selections a world-axes aligned bounding box is > more what we expect. > However, I have a doubt why we handle images different from meshes or point > clouds. If those objects have their proper coordinate system, why shouldn't > we align to this system if the user selects explicitly one of those objects? > > Can anybody explain / remember the reason for this choice? > > Thanks, best regards, > Daniel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > mitk-users mailing list > mitk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mitk-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
