sure thing, I created an example for you where I create this behavior with one output. It should be relatively straightforward to adjust your code accordingly.
Thanks, that surely got me in the right direction.
One issue: Iām also showing/hiding ādimensionā assets which have html-text linked to them.
With the previous viewer they would also disappear when I toggled them off, but now they wonāt.
I found out that itās the ātag2dā outputs that need to be toggled, but setting āvisibleā to false wonāt cut it there.
The code snippet Iāve been trying:
session.getOutputByFormat("tag2d").forEach((item) => {
if (!!item?.name.includes("DIM - ")) {
if (typeof item?.node?.visible === "boolean")
item.node.visible = false
// setting this to false won't hide the text-items
}
})
Hello @post8
thank you for letting me know about this, there definitely seems to be something going on. Iāll get back to you with a solution!
Cheers, Michael
We are aware of this issue and have it filed in our backlog. When Michael comes back he can give you a better estimation of when this fix can be released.
Thanks!
Another thing Iāve noticed is that when the geometry is updated (by updating a parameter), the dimension assets become visible again.
(Iām currently keeping those assets invisible with an always running interval, which is far from optimal.)
regarding your first issue, this happens due to an issue with the visibility check that we currently use. A planned restructuring for that is in our pipeline, but this might take a bit longer. As a workaround for now, you can look into creating more space for the dimensions tag, by creating a wider gap between the lines. That should help with the flickering.
For you second issue, how are you currently applying the visibility?
In this example we are using the updateCallback function to re-apply the visiblity of an object. I think this might already solve your problem.
your message had a great timing. This issue has already been fixed and will be in our next release which will probably happen next week. Iāll message you here once it is publicly available.
I gave it a try today and I stumbled upon the following issue. When updating parameters, the previous values are not being removed as can be seen in the following sandbox:
One thing I have noticed is that when I hide the dimension assets (āglbā and ātag2dā) by setting āvisibleā to false, they become visible again whenever I update the model parameters. This behaviour seems different from what I remember as the default.
Am I correct, or could it be related to a configuration in the ShapeDiver model?