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
Hi Kike,
Just dealing with this issue now as well. I appreciate the effort you put into this, but this is, pardon my french, a horrendous feature that can only cause trouble. Right now I have parts of my script expiring when I absolutely don’t want them to.
Now, this turns every possible component into a “dynamic pipeline”. If this feature is not completely discarded, this should be a hidden feature for advanced users, and not a default true . In the latest WIP I can’t even turn it off.
I love a lot of the features in the native Rhino Tab components, but some are also trying a little too hard to be “smart” which often obstruct my possibility to get the scripts to work like I want them to. This means that I’m still relying on Human or custom scripts, which I would really like to avoid.
Edit. to add to the chaos. Say I take the geometry using the Model Object component, then I get a referenced geometry out. If I now put that into another component that casts it to a model object I suddently get another “dymanic pipeline” - behaviour. It’s a nightmare.
After @martinsiegrist comments this feature has been turned off by default on the latest v9.
This was on always in v8 and impossible to disable.
I keept the possibility to explicitly turn it on in case anybody still needs the previous behavior.
