Components, Layers and Component Collections

[aadbuild]

Hi everyone,

I have encountered a small glitch and I'm sure there is a very easy way around this but I don't seem to be able to get it right. I think I have done it before but can't retrace my steps.

I am creating a custom component collection and I want to be able to drop a component into any one of my models and for that component to automatically create its own layer in my layer manager. I have tried drawing the component and assigning the appliances layer to it before it is saved in the collection however when the model is placed within a new model it will always be assigned to layer 0. But when the model is exploded it is on the right layer. I have also tried just drawing the component on the desired layer and saving it to the collection however, that has not worked either.

What am I doing wrong? Could someone point in the right direction? Is it the way I am saving these components that is wrong?

Thank you!

[Gaieus]

Hi Andrew, could you show such a component?

[Alan Fraser]

Andrew, one quick suggestion would be that you not only have the component geometry on the custom layer, but that the custom layer is the current active default layer when you save the file.
If this isn't practicable....maybe you're constructing the component in a file with a load of other stuff....then save the component out of the browser, open it up on its own and make sure that its custom Appliances layer is set as default before re-saving it.

[dedmin]

[Alan Fraser]

All the stuff at FormFonts (except for the really early models) is on a FormFonts layer...and it imports on that layer without the need to explode anything. This is because it is actually modelled on that layer...because we have a FF template with that layer set as the default and Layer0 just sitting there doing nothing. If all else fails, I'd suggest developing a similar system. That way you know for certain that every face, edge, component and group are all on your custom layer and that layer is the default for that model. It can't fail to import properly.

[Richard]

Alan - I'd heard that everything is on the FF layer, sort of surprised in a way that a layer structure wasn't adopted from your category structure!

[aadbuild]

HI all I tried your solutions unfortunately with no result. I have made a component on the layer that I want it to be on I then saved it to components folder in Su7 . I then reloaded it and it still is on layer 0 . It will creaet a new layer and when I open the component on layer 0 it shows that the geometry is on the correct layer but the actual component is not. This makes it dificult for reporting componets by layer.
I have attched a simple component for you to have a look at and a wmv. showing you how I created it. this is a quick example of how I am creating the desired component
I ahve also edited the component in Su7>componets>and came up with the same result.
SOrry for taking so long to get back. I have been try several methods to do this.
thanksbasic component as per wmv

[Alan Fraser]

Andrew...you're absolutely right. I'm pretty sure this is a change of behaviour regarding layers. There now appears to be no way of getting imported components onto the correct layer automatically on import...you have to move them there yourself. I don't think this is the way things used to work; I think something got broken; and I've posted this topic in the beta forum to see what Google can come up with. Hopefully, they'll find a fix for it. It would be quite handy if they could also fix the bug that puts everything saved from the browser onto Layer0 (regardless of what layer it's actually on) at the same time.

[plot-paris]

actually, there is a very simple explanation to that.

if you place a component in a model and then put it onto another layer, this information is applied to the 'outside' of the component, but doesn't affect it in any way. its pretty much the same when you apply a colour to a component.
lets say you've got five copies of the same component in your model. now you paint one of them bright red. only this one component changes the colour. if you want all the others to asume the same appearance, you have to enter the component and actually paint the content, not the component itself.

thats like if you've got 10 eggs. where you store those eggs (whether in a proper egg carton or in a velvet cloth) or if they have been painted for Easter... all that doesn't affect the eggs themselves...

so if you want the eggs to be red and wrapped in carton, you have to store them that way - a carton with red eggs inside.

or to translate it back to SketchUp: you have to store a component, with a group inside, thats painted red and placed on the desired layer...

I hope that made sense to you (and I didn't explain something that has been known already)

[TIG]

SUp is doing it right. A component goes on the current layer - and that's usually Layer0.
The recommended way is to have your 'raw-geometry' on Layer0 and then put groups/component-instances on the desired layers... That way you can have the same joist used on several floor levels that each have their own layer...
It's easy to fix this - select the instance and get Entity Info, in the Layer Info change it to the layer the raw-geometry has OR any other layer you desire...
You can force it to import it as component on a set layer by editing the component file and making it all a component on the layer you want, you explode the imported/inserted compo after placing it, thereafter you have the one you wanted on the right layer... Messy!!!
Easier to change its layer using Entity Info after placing it OR change your current layer to put it onto the layer you want initially...

[Alan Fraser]

I guess I must have been having a senior moment...probably confused by the fact that all the FF content disappears if you turn its layer off, because that's where all the geometry is.

[aadbuild]

thanks for all the replies, I can see why it is standard this way and for good reason. Say I take the egg example\

@unknownuser said:

so if you want the eggs to be red and wrapped in carton, you have to store them that way - a carton with red eggs inside.

I guess what I am asking is... Is it possible to get the chook to lay the right colour egg genetically.(ruby?) Or is it possible to tape a red bucket of paint to the chooks bum?
I am not suire if you guys have read my other posts but I am trying to piece together the BOM puzzle and if it where possible to save a component to a layer and have all the componet be on the layer it would help me coalate the information with out manually going and changing it to its own layer. SOmetimes a model will have 500 components. If i had say: all the toilets on 1 the pc layer, when I did the take off I would know i had 30 toilets to order (preferably without having to manually having to change them to the correct layer).
When i first started this post i thought i was doing something wrong. I do remember downloading componets from 3d warehouse and they were on there own layer. may be it was just the geometry. Has sketchup changed the way it does this between su 6 an su7?

[TIG]

To stop SUp adding component instances onto the 'correct' layer [the current layer] you need to invent your own 'component-inserter' browser... So say if you want to insert a joist you DON'T do it from the Component-Browser, but from your own 'component-inserter' browser... that way it it can fix the joist's layer as you might determine - from it's 'type' or from a dialog asking for the layer ? ...
Alternatively you invent a complex observer that spots whenever an instance is added to the model and sets its layer to suit something - like the instance.definition.entities[0].layer ???
If you explain exactly where you want to end up, and where you are starting from, then the solution might be more obvious, or at least clearer...

[plot-paris]

or you can do it the dirty way...

create a component within the component. place this inner component on the correct layer. call the inner component by the correct name (e.g. toilet) and call the outer component something like 'toilet_container'.
now you've got everything you want:

• when hiding the layer 'toilets' all the toilet components will become invisible.
• if you check, how many of those toilets are in the model, it will show you the right amount
• when placing the component, you don't have to mess around with layers. they are already placed

there are two downsides though. firstly, you've got an unnecessary component in you browser (the 'toilet_container' component); and you actually have to expand your view in the component browser in order to see the ones you want, which clatters the browser with all the nested components as well. good thing is though, that it won't increase the file size too much, for the content of the container component is just another component.
secondly, if you press Ctrl + A to select everything within your scene, even with the toilet layer switched off you will select the container components (even if they are not visible). that may cause some unwanted deletions if you are not careful.

you could of course always explode the container components. but then its not too much of an effort to simply place the component on the right layer manually in the first place...

[aadbuild]

Oh and Tig I am not disputing that layer 0 is not the correct layer for componets to be placed on. I am simply asking if it were possible to have it on the layer I decide not the layer Sketchup decides.

[aadbuild]

@unknownuser said:

If you explain exactly where you want to end up, and where you are starting from, then the solution might be more obvious, or at least clearer...

Sorry if I sound a little vaigue. basically, from start to finish:

1. I have my own library of components that I use for all my models.
   2.I place the components in new models and I report the components by layer ( with a ruby).
2. The problem for me is: when I import a new component from my collection I have to go and manually change from layer 0 (the "correct" layer thanks TIG) to the layer I initially saved it on so that the component is where I want it to be in the report.

There could be 500 components which takes some time to adjust even If I do it in outliner. It also brings a lot of human error into the mix.

A 'component-inserter' browser is above our ability and probably more complex than I have time to tackle. Thanks I appreciate the suggestion though.

oh and plot paris I like the dirty idea, thanks. it will get me out of trouble until I come up with some thing new

[chrisglasier]

Andrew, please consider this what you might call low tech solution.

Use the word joist to indicate you need a joist. Add dimensions, either exact or for later adjustment. Make a component say 50 x 175 x 1000mm and save it in a file called joist.skp. Arrange it so that when you click on the word joist you can also click on other words that link up to functions to import it into your model, scale it, make arrays, and so on.

When you have made more components in this way, you can collect them together under another name, say structure or floor 12 or timber. One component can belong to as many collections or groupings you care to name. Dimensions and labels would need to go on layers because they are part of drawing rather than components, but everything else can go any place because you are able to generate only the components you wish using the collection, grouping or component names you have selected.

Rather than extract a BOM a BOM generates** the model ... and with other devices just about anything else you need to support physical activities.

You and I have talked about this for more than a year, but now my cavalier attempts at coding have been taken in hand by Jim and we now have a Web Dialog/HTA/In browser operating system that we both consider stable, extensible and of universal application. You can see the first application here, but probably of more interest to you will be the machine that is suitable for more "horizontal" associative indexing - e.g. from project through to door hinges rather the long "vertical" lists of Classes and Methods in the API device.

The problem lots to do makes it difficult to know what to do first - the API devices like plugins index to show off the functionality or, for me the more interesting, general purpose machine

and building industry devices that I think are of interest to a few here.

My regards

Chris
edit ** or modifies - can just hide/show

[aadbuild]

Thanks Chris I do like the way name sets makes it easy to organise components, layers and variable tasks. I am still trying to figure out where the web dialogue box fits in. I guess my need for a BOM is to know which components are in the model and have them in a way they can easily be grouped acording to supplier and the job progress. I do this by using layers (more of a named group) as the job stage. It would probably be easier to do this with namesets but I have not spent enough time lookig at how it would go together . I guess the only way would be to give it a go...
would you lke a model example? and we can compare notes. Your way verses mine?

[chrisglasier]

@aadbuild said:

... I am still trying to figure out where the web dialogue box fits in.

This little thing can sit inside a web dialog to make it easy to give Sketchup commands like in the .rb file attached. The function of the machine is to knit a nset (nameset) of all the things you associate with yourself in a top down hierarchy. So one trail from the name office would go:

Office>Projects>Project 1>Building>Ground floor>Space> Sanitary ware>WC suite.

Of course there would be many trails like this with inherent and custom cross links. For example, sanitary ware is an inherent link you can use to pick up all the sanitary ware but you might also set up a "week1" name and link all planned deliveries (possibly including sanitaryware). The menus on the right pick up devices both to build the nset and use it to assemble models, purchase orders and so on. So Add is obviously the first device I need to make.

@aadbuild said:

I do this by using layers (more of a named group) as the job stage.

I understand but plain text is king if you want to use it for many different tasks. Doming plain text (making into HTML) means you can automate what you otherwise have to do by hand (in Excel for example).

@aadbuild said:

I guess the only way would be to give it a go...
would you lke a model example? and we can compare notes.
.

Yes of course and I am working towards that. I already have one of your models but I don't think it sensible for me to strip out its attributes into a plain text list (for converting to json) better to get on with the machine. But a snapshot of your components subdirectory would be useful to see whether we can easily adapt and incorporate your naming system.

@aadbuild said:

Your way verses mine?

Actually we both have similar aims so I think it's more like pushing the thing to a natural and satisfying conclusion. But a little rivalry is healthy!

Chris

---

Namesets3.rb

[chrisglasier]

@chrisglasier said:

But a snapshot of your components subdirectory would be useful to see whether we can easily adapt and incorporate your naming system.

I wonder, Andrew, instead of a screenshot, you could copy six of your component files into a folder, zip it and send it to me. I hope these pics and notes will help to show where I'm at and why such a folder made by someone else would be a good design prop.

What I want to do next is to get the machine to read the file names of your components, strip them of .skp and populate the product (component) names slider with the results. So after this step the machine will be a component importer and instance namer. At the same time of course it keeps a tally of the numbers. After that I will make it into a kind of super measurement box, and then a means to hide and show components by entity (location), grouping (purchases), headers (subjects) or individual component. I am not intending to get involved with positioning and rotations as before, but I have some code worked out for tracking resizing in Sketchup (so actions are bilateral).

My regards

Chris