Hi, there is no recommended way for wrapping ITK reader, especially since MITK is doing that already. Why would you want to wrap the ITK Nifti reader again? (maybe there is another approach).
In general, you would create our own Nifti reader, associate it with the mime-type name mitk::IOMimeTypes::NIFTI_MIMETYPE_NAME() and register it with a higher ranking the MITK's one (which defaults to 0). Best, Sascha On 01/29/2015 05:11 PM, Miklos Espak wrote: > Hi, > > we have a custom NIfTI reader, and MITK also has one. As I see, the > activator of the the MitkCore module goes through the ImageIOs > registered by ITK, skips the nifti one and registers MITK's own version. > > What shall I do to replace the MITK's nifti reader with ours? > > I tried to mock what's in the CoreActivator, but it uses > mitk::ItkImageIO that is an internal class. > > Is there a recommended way of wrapping ITK image io-s? > > Cheers, > Miklos > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
