Hi there, please can someone help me understand these changes:
http://mitk.org/git/?p=MITK.git;a=commitdiff;h=05141565fbe7df618626569d0af54a616e0c025a http://mitk.org/git/?p=MITK.git;a=commitdiff;h=86687c4d22e86c213334f36c1ad553159254b343 The reason I ask is that I have my own plugin to manage lookup tables, and I instantiate an mitkLevelWindowManager and connect it to the data storage. Previously, it was the top most visible node that was considered the selected node, so that changes to the level/window applied to that node. This appears to have changed. These two diffs shown above introduced a new property imageForLevelWindow on the actual data node, and then this appears to cause the mitkLevelWindowManager::m_AutoTopMostImage in my LookupTableManager (not the one created in DataStrorage) to revert to being false which changes the expected behaviour. In other words (by which I implicitly mean "as far as I understand it"), the fact that we are storing a property on a data node, stops you from using two Level Window managers, as the property is shared via the DataStorage. This appears to be either a wrong design, or something I have misunderstood. Please can someone take a look? Thanks Matt ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
