It is now many years, later, the current version is SketchUp 2017, yet I'm still seeing the exact same issue with a complex dynamic component. The basic problem is that there are no global attributes in Dynamic Components: only local attributes that can be seen one level up and one level down in the hierarchy. I thought that this severe limitation could be bypassed by creating some lower level attributes the refer up to "parent!" attributes at a higher level, and others at higher levels that refer down to "child" attributes at lower levels, but it does not work. SketchUp does not traverse the entire hierarchy in both directions with each refresh or "redraw": it only seems to go down each branch once, so lower level attributes cannot be passed up one branch and down another. Thus, the ONLY option is what the original poster already discovered, years ago: calculate all attributes at the highest level, and then pass them down each branch. There's no way to reliably pass things back up again, nor to pass things between branches of the hierarchy. It's a great pity, as adding the simple functionality of global attributes would solve the problem entirely, and completely avoid the need to be passing things around between levels! Hopefully one day the SketchUp developers will figure out how to implement global attributes. Is this product even still being developed? There doesn't appear to have been any changes or updates to it at all, in YEARS! I have seen changes to the version number each year, but precious little in the way of new features, or even bug fixes. Is this a dead product? In the meantime, your solution is the only way that works.

@pcmoor said: if using in the context of lenz attribute and assuming using cm, then value compare current("lenz")*2.54 lenz = if(current("lenz")*2.54<=240,240,if(current("lenz")*2.54<=270,270,if(current("lenz")*2.54<=300,300,360))) if calculating a nearest_size attribute without forcing the lenz to snap to the result, then use size = if(lenz<=240,240,if(lenz<=270,270,if(lenz<=300,300,360))) Sometimes, I think I'm smart, and then someone proves to me I'm not so! Sorry about the delayed response mate, I just got to try that and bang, works a treat!!!!!!!! You are a modern day superhero!!!!!!

Hello Slightfoot, Attached the solution exactly as requested made in Sketchup2013, enjoy! A little bit too late i guess ha? DC with cut-openings-holes frozen vs scale.skp

@pcmoor said: here is a panel DC within a working file that can be scaled or fixed and set to different pitches and returns the dimensions in the option dialog Use the fixed position (drop down option) to start with, then use the scale position to match the next panel (direction via another dropdown) (its not fully tested, so if there's something not quite right...its fixable) I can help you if you private message your DC with regards the work flow, the report writer can transfer the required data to excel. Excel can hold the formatted label, exactly as you have shown with named cells in the data positions. An VBA routine can be made to transfer the data sheet from Sketchup to the labels required, in that Copies be made in excel and filled out to suit each component that exists on the report I am well acquainted with excel and VBA P.S. most likely would build this DC differently, however it does give you an idea to how to achieve your goal Thanks so much mate, and I will likely seek your employ to help out with this! I did workout how to easily apply the data to the sticker through a simple word doc using mail merge. Though totally open for a more streamlined option. I'd certainly like to see how the DC can be better constructed and function. We didn't plan on having it scaleable as we were planning to stick with blocks made of standard dimension panels so we can see exactly what is constituting the makeup and switch out say a 2.7m panel for a 3.0m panel when they exceed the height. I've now got to jump in and upgrade my SU license, as I haven't since I left the test team after 10years and by doing so I got the demand to buy a whole new license, rather than just move to the maintenance program! It just went against my grain!

Is this a question about Dynamic Components? or a general question about how to make a sphere and why it is failing? If it is a general question then it is down to you attempting to make the sphere too small. Read the thread called The Dave Method in the Tutorials section.

Thanks!

https://forums.sketchup.com/t/controlling-list-ordering-for-component-dialog-box/49079/3

refer to http://sketchucation.com/forums/viewtopic.php?f=289%26amp;t=68004 otherwise if specific you need to upload your component (private if required, note I will be away two days)

That is exactly what I was trying to do. Your now on the "Legend" list. Thanks mate.

Method 3 somewhat follows the line of reasoning of method 2 create rectangle 900x50 and pushpull it 100mm, make it a group "middle" create 45deg wedges either end, groups "bottom mitre", "top mitre" [image: HWhF_Capture.PNG] make it a group called "side" and create the relationship / formulas, again I used parent as I intend to copy and make unique sides [image: Bhdf_Capture2.PNG] now hide the joining geometry and group, this then in formation should be similar to the side in method 2, but mitered rather than over lap [image: ZRcJ_Capture3.PNG] do the rotate @ 500mm as before, copy(control) *3 [image: 1mqW_Capture4.PNG] change the group instance name in both model info and the attribute dialog [image: 5gus_Capture5.PNG] it is important to confirm that the groups are unique (changing the instance name or position may not create separate definitions (the copies initially share the same definition, that relationship needs to be broken) so pair each one and right click make unique [image: 7MVQ_Capture6.PNG] now make all the unique sides a component, "frame3" fill in the relational formulas [image: 9K6o_Capture7.PNG] completed example attached frame 3.skp

Philip, I tried the solution you posted above, but ended up using 2 AnimateSlow on a single onClick. I didn't know one could use the semicolon to have double results from one onClick function: [image: KpTO_RevolvingandSlidingDoor.gif]

Thanks that was really helpful. When I force the component redraw it's all good.

perhaps you could make your own? a ruby snippet: either use ent or sel test in the ruby console ` mod = Sketchup.active_model # Open model ent = mod.entities # All entities in model sel = mod.selection # Current selection dcs = $dc_observers.get_latest_class ent.each { |e| if e.is_a? Sketchup::ComponentInstance dcs.redraw_with_undo(e) end}`

YES! I see now. That is some pretty sweet re-engineering of the pretty remedial string functions! I do wish FIND would just return FALSE if the string is not found but oh well. Thanks Again pcmoor!

Thank You Jim! So how about if I wanted to find out if the string "SINGLE" exists anywhere in the string?

@gaieus said: Szia András! ... Remember where you save them, go there and open the component just to see that they are now just a simple file (without being a component inside the file). .. when you drag some dynamic component from the file manager to the sketchup windows, it seems to lose its dynamic characteristics your explanation solves the problem: just explode once the dynamic component you just dragged into sketchup, and the dynamic characteristics are available again thank you, this is a big help but how do you make sure in the first place when you register the component, that it is "just a file", and not a "component in a file" ?

Had anyone the same problem? maybe it possible to write a custom script to measure the area and attach it to DC?

Perhaps not very clearly explained what exactly is needed. I think so more clearly. [image: MSCj_2017-05-13_15-36-262.png]

@unknownuser said: This Bounding Box includes rotation, so X, Y , Z sizes are not object sizes. Is there a way to get exact sizes of objects (or groups,entities.. any kind of selection)according to local ("objects") or world coordinate system? (Sorry if my terminology is wrong). Here is my solution: b = instance.definition.bounds t = instance.transformation x = ((b.max.x-b.min.x) * t.xscale) y = ((b.max.y-b.min.y) * t.yscale) z = ((b.max.z-b.min.z) * t.zscale) Hope it helps Have fun!

@unknownuser said: There was a lot of debate about this before launch. We wanted DCs to follow the rules of SketchUp as much as possible. So the question became: "If I have 3 DCs in a model, and I scale one of them, should all of them update? Or should only the one I scaled?" ...In the end, we thought it would be more frustrating to have every instance in the model update instead of just the one you scaled. We've talked about adding some kind of toggle that would allow you to choose which behavior you prefer. Any thoughts on that? Do you guys think we did it backwards? I'd love to hear your ideas. No, you didn't do it backward or forward, you just didn't work it out at all. The only logical solution would be to scale the one DC WITHOUT BREAKING THE LINK TO THE ORIGINAL COMPONENT DEFINITION. It is essential to design workflow to be able to go back and make changes to ALL elements throughout a project in a quick and centralized way. As budgets change, design options are accepted/rejected/marked up, and products enter or leave the market, the ability to edit a single entity and broadcast that change to all instances in the model could save hundreds of production hours. I am actually really surprised to discover that this is how DC work and the whole scheme is actually intentional. I am not a programmer but I don't understand why this could not be fixed? User Defined attributes can already feed sub-entites data, like LenX for a certain sub-group can be set to the User Defined attribute "MyLength" so why should it matter if one DC has "MyLength" set to 20 when another is set to 30? I must be missing something here? Revit and AutoCAD have this ability baked into Families and Dynamic Blocks already. The both use dimensional constraints and user-defined parameters to set the contextual "data" of an entity and objects within can be set to react to that context in different ways. And I think a "Component Replacer" is more of a band-aid approach than an actual solution. If it could be written as a 3rd party script (I believe ThomThom already did), it would have to not just reset the definitions of all the bastardized components, it would have to note and re-create ALL of the attributes of every component in the model so that all the scaling, visibility, etc. of various components would not be lost in the re-writing. Please tell me this has already been worked out in SU2017 or something and that is why there has been no further dialog on it!