FeatureComputerManager should read the data graph to determine the type associated to a SegmentationResult
There is a problem currently in the way FeatureComputerManager (FCM) recognises the type of object which is associated with a given SegmentationResult object:
At the moment FCM creates a property 'Associated Objects' which corresponds to the declaredType() of the SegmentedObject that it creates for a given SegmentationResult. The problem is that when the user wishes to go back and recompute features, the user will delete the data objects, but the 'Associated Objects' property in SegmentationResult will remain and FCM will not allow the user to create new objects again.
Deleting the 'Associated Objects' property as a workaround is fine if there is only one type of SegmentationResult. If there are several, then the property is also deleted in the SegmentationResults which are not concerned by the change, so this leads to quite a few issues.
While there is a trigger system planned for dealing with this type of problem, an alternative could be to make FCM check whether the SegmentedResults of a given 'Segmentation Type' are actually connected to SegmentedObjects.
To make the method available for all consumers of SegmentationResults, a static method in UsefulQueries (in API) could be created.