In my plugin, I have a DAG which inherently can't be evaluated in parallel ( due to the dependencies ).
however, there is an strange issue with the nodes possessing `kTime` attribute.
I'm adding the currentTime attribute through this code which is connected automatically to "time1.outTime" plug.
aCurrentTime = unitAttribute.create( "currentTime", "ct", MFnUnitAttribute::kTime );
unitAttribute.setHidden( true );
unitAttribute.setKeyable( false );
addAttribute( aCurrentTime );
attributeAffects( aCurrentTime , outputAttrib);
Everything is OK unless the node with time attrib gets added into the middle of the stack ( not the last one ).
It tries to evaluate all available time ranges ( e.g 0 to 5 sec ) in parallel. I know it's related to cached playback but more strangely, it starts evaluation again when a (slider of ) float value of a node is modified, it doesn't matter if the node is above or below in the stack.
Any suggestion? Is it a bug?
