Dear MITK users, the current MITK master contains changes which alter the behaviour how MITK classes derived from itk::LightObject are instantiated via a call to ::New() [1].
Formerly, the New() method asked all registered ITK object factories to create a suitable instance, which is kind of the default for ITK classes. However, this approach led to some (severe) performance penalties in certain MITK scenarios and the capability to "override" the implementation of a MITK class with another implementation has not been used in any known MITK project. Therefore we decided to replace the old New() implementation with a "factory-less" implementation which ignores object factories a just calls "new" directly. If you are relying on the default New() behaviour of some MITK classes, i.e. you are replacing MITK class implementations with custom classes, please let us know. We can either re-introduce the standard ITK new behaviour for selected classes or provide another mechanism to re-enable your customizations. Thanks, Sascha [1] http://bugs.mitk.org/show_bug.cgi?id=17339 ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
