Hi Gerald,
this is a current design problem that we are aware of: New datatypes and the
corresponding factories can be defined by external modules. But not all core
classes support additional datatypes. The level-window manager, for example,
hardcodes the list of datatypes it recognizes. This can be seen in the function
mitk::DataStorage::SetOfObjects::ConstPointer
mitk::LevelWindowManager::GetRelevantNodes()
The class is then checked by the GetNameOfClass() function and not by a dynamic
cast. You could locally append your datatypes to the list in order to enable
the level-window manager for them. Of course this is not very convenient. I
will file a bug regarding this issue and hope that we can resolve this issue in
the future!
Best regards
Klaus
Von: Lodron, Gerald [mailto:[email protected]]
Gesendet: Mittwoch, 28. Juli 2010 07:44
An: '[email protected]'
Betreff: [mitk-users] Inheritance of mitk::Image
Hi
I want to store some additional information to mitk::Image so i made my own
class called CMyImage which is inherited from mitk::Image.
It is surprising for me that this new data is ownly painted in the axial,
coronal and transversal view. The 3D Image plane widget and the level window is
missing!
Can anyone say me how this could be?
best regards
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
