@unknownuser said: and I surely forgot about it. Easy to do - SketchUp is complex, regardless of what the marketing team says.

I don't know if this would help but the following Input uses a single attribute to set the value taken from Input_val; if less than Min then Min is used, if more than Max then Max is used, otherwise the Input_val is used - not ideal but it might help reduce your code a bit: =IF(Input_val<Min_val,1,0)*Min_val+IF(Input_val>Max_val,1,0)Max_val+Input_valIF(Input_val>=Min_val,1,0)*IF(Input_val<=Max_val,1,0) Regards, S

If you enter a value (without an = sign), in the Component Attributes dialogue, just before you Save the Component it will be 'remembered' when the component is placed and will remain visible until changed by the user; is this what you mean?

You have it right. It's an inconvenience and makes things more complicated than need be. I think I made a suggestion to Google one time about adding a type of global variable to DC's; or possibly making a variable's scope be from the parent down to children of any depth, but not up to parent components.

@unknownuser said: If I make a model which I will need for further usage, I'll make it Component, to see it in Component Browser (and of course, I will save it in my Collection), but its inner components will be groups, otherwise my Component Browser will be filled up with all sort of C.Definitions that I don't need. Well, there are exceptions from this rule... But now is clear for me when to choose to use groups. There are indeed exceptions to that rule. In my work flow I only use components but I'm mainly drawing furniture to joinery level detail. All of the parts of a piece of furniture will be components even if there is only one instance in the model. i.e. a table top. In addition to the assembled model, I make exploded views and detail views. With the exploded views I will end up with an additional instance of the table top. If, as commonly happens, the client wants changes after the model is made, I don't even have to wonder if the changes got made throughout the model. Few opportunities for errors that way. As to the Component Browser being filled up with component definitions, I've never found that to be an issue. Do keep in mind that components you've had in the model, even if they've been deleted from the model space, will still be shown in the In Model library. This is handy if you inadvertently delete the component because you can get it back. On the other hand, if you know you don't want those components, you should run Purge Unused or the Purge All plugin which will does as it says.

Yes you specifically need solid object you don't have to worry. If you do need a solid once, and you can't work out why it's not a solid, you can use this plugin: http://forums.sketchucation.com/viewtopic.php?f=323&t=30504

@sketchdata said: Looks good, I think you're understanding DCs. Can I ask if you did your attribute "Display Values" in "English"? I noticed some other language on some of the component names. I have a reporting plugin and trying to resolve language issues. Also a thanks, your HTML markup inside the DC attributes helped me realize I need to modify my reporting plugin. Values are displayed in metric units, but inside, in Component Attributes, you can see some names in other language (Romanian). I translated only what I considered the user will see/interact. I was tired and in my head I had only DCs Nice component reporter tool! I would like to keep close with you about that !