How to hide components from teh Components Manger?
-
No, what I want to do is hide some components from the Component Manager. Similar to how the default SU components do it.
-
That is what the expand toggle does I think??
Bob
-
No, the expand button let you see the hidden components.
-
I'm wondering if this is new behaviour. It's certainly the case that if you Import a skp rather than opening it, you only see the top level component, not all the sub-components.
But I was kind of under the impression that's what happened anyway when actually constructing them...that if they were bundled-up into a higher level component, all the constituent parts disappeared. Maybe my memory is going. -
Yes but it only seems to work with imported geometry not native (i.e. made) within your model.
-
Maybe the component has to be created while inside the top component..?
I'll have a go and see what happens if I export an component and then import it. (this would still not be ideal as it makes for an awkward workflow...)
-
Just did a quick test:
Imported components will hide their sub-components.
Creating a new component while within an existing component will not hide it.
I wonder... maybe a ruby script can access the properties that controls this..?
-
True it would be more handy if SU in this case worked more consistently. I also tend to create extremely compound models from tiny bits of components and this would allow me to browse the browser (
) more efficiently. -
Just came across this:
@unknownuser said:
Hi,
In the Ruby API docs, there is this ``hidden?'' method for components:
hidden? The hidden method is used to determine if this component definition should be hidden on the component browser.Is there a way to tell SU that a component is not to be shown in the browser?
So it looks like a ruby script might be possible.
-
Let's hope some of the ruby gurus chime in...
-
To fix it manually you can Save_As the nested component [made of sub-components] 'externally' (you just hover over its icon the the compo'browser and select off the context-menu...). Then erase any instances of it and purge the model of unused compos. It and it's sub-compos will purge if they haven't got instances. Then import the externally saved comp back in and now you have one compo that's made from several nested compos BUT only one compo shows in the browser !
-
The problem is that doesn't work well with my workflow. I'm using V-Ray for SU and when you import components it won't import the V-Ray materials.
If I get time over the weekend I'll see if I can learn enough Ruby to make a script for this.
Advertisement