Hi Dieter, On 01/15/2014 04:19 PM, Dieter Menne wrote: > I know that Par/Rec is a version mess made worse by our own legacy files > which report the version incorrectly, but I had already solved that problem > by patching the files in ITK/Modules/PhilipsRec in a test environement. > > So after looking into the code, I thought that the following could work: > > a) add a private factory following the > NiftiImageIOFactoryRegister__Private-scheme to itkPhilipsRecImageIOFactory > b) Add the private class reference to the list in > itkImageIOFactoryRegisterManager.h > > > I am aware that the registration of the extension might result in ambiguities. > > Do you think this is a valid approach?
I am not familiar with the private class reference mechanism within ITK, but if you could get your PAR/REC reader version registered that way, and the ITK factory mechanism returns your reader version when asked for a suitable PAR/REC reader, MITK should automatically pick that version up. That having said, we are currently working on a new and more flexible reader/writer system for MITK which will support such kind of scenarios out of the box. Best, Sascha ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
