What’s the necessity for this feature?
I think a component should highlight when synchronizing is turned off but at the moment it seems the symbol is there all the time.
I’m not sure if the symbol even needs to be visible on a downstream compononent. It only clutters the canvas.
Would love to get some insights from @kike or @AndyPayne on this.
PS: Did you turn off recomputation when referenced object visibility changes in Rhino?
Hi @martinsiegrist,
I’ve been doing some changes to improve when things expire in response to a change in the model.
In v8 when a layer color is set any Query Model Objects that contain an object on that Layer expires and all the components after it are reevaluated.
In v9 only changes on the object itself will expire the result of Query Model Objects. This is like this also in all the other Query components.
The way is exposed right now is to ensure things behave as before even data is expired in a more selective way.
Now the user may decide on which points of the definition data may expire. You can turn on and off synchronize at each output.
But I see your point and maybe the default should be with all these outputs turned off by default when you place the component in the canvas the first time.
Thanks for the quick reply.
I think the option for less recomputes is needed. I like that I can show / hide an object in Rhino and it does not recompute every time.
The two main options could be
With sync turned off, a component with option to what change to listen to could be used for a more selective recompute
