As it is the case in GetConstProperty, where the BaseData is searched for a property, we should find a solution with GetPropertyKeys() to return keys of BaseData and DataNode.
Description
Related Objects
- Mentioned In
- rMITK861611779b17: start to rework PropertyRelationRuleBase
rMITKd07d0411aac9: Fixed StatisitcManager test
rMITKdb337f4c73db: Added new image statistics plugin
rMITK50b86895829f: Added new image statistics plugin
rMITKb61ff0d67b59: hotfix before T24729 is done
rMITK1460f6aefb4a: workaround for T24729
rMITK98d127f9d268: hotfix before T24729 is done
rMITK48caf381e41a: workaround for T24729
Event Timeline
Because GetPropertyKeys is part of the Provider interface, I would implement it exactly the same way like the getter of the interface.
The problem/risk arises with the setter and they are part of the PropertyOwner interface. Therefore I would propose the following:
- extend the Owner interface by a method IsOwnedProperty (see below)
- Add the documentation to the DataNode, that 1) one should use it to check via this method if the property is realy part oft the node (this method does not pass through to the data) and 2) that one should be carefull if modifying props that are realy owned by the node. Otherwise one would accidentally overwrite/hide base date props.
IsOwnedProperty(const std::string &propertyKey, const std::string &contextName = "", bool fallBackOnDefaultContext = true)
@kislinsk: what do you think?
Hi there! ๐
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. ๐
Best wishes,
The MITK devs
Hi there! ๐
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. ๐
Best wishes,
The MITK devs