i finally found out how to do this.Thank you so much Dave for giving me the solution. Bothered me for a long time. Works fine now.Thank you.

You can still install a 'beta' version in the correct way... Or get the latest most current version and install that as I said. Whenever I might have installed a 'beta' version I've done it as I explained and I've never had such problems...

Super Halroach! Actually I allready found/tested that setting but did not click interact twice.

Sorry of the late reply Epix. In Sketchup's Component Browser, in the In Model view, you can right click on a chosen component and 'Replace Selected'. I don't think it would maintain the scale of the components though, only the placement point. You would also have to select all the relevant components in the model first. You might find this (ancient) selection plugin useful: http://sketchucation.com/forums/viewtopic.php?p=62531#p62531 We've had some thoughts of adding a mass replacement feature into Component Finder like you need, which would also maintain the scale of the components... have to get to it. There is the FlexSlider component. There are other sliding door typologies we haven't gotten to yet. If you have one you'd like to see Flexed, send it by email. It would be very helpful.

Hi - with this bottle topic I also struggled some time ago I am not sure, but I think I had seen a great tutorial from forum member Cotty and afterwards I made my own attempt, which I then posted in the Shaderlight Forum (see link below) http://www.artvps.com/index.php/discuss/viewthread/1332/ There I also documented my done steps, which are also to be found in the 3D Warehouse. I hope this might help... https://3dwarehouse.sketchup.com/model/u8f043c9d-8b88-4633-94ff-a10b114fdef6/Bottle-PET-Bottle

A quick look tells me your issue may be related to your incorrect use of layers. Worth reading up on them too.

@unknownuser said: I try to reason how this works but it doesn't come easy to me. It isn't easy. there are a few bugs to get your head around. Perhaps it's helpful to understand that the dynamic part is a ruby script add on, it's not hard wired and as such has to work within the limitations of the ruby language and the developer's understanding when it was conceived. There are disconnections between what an attribute reports and the updated SU view, for example changing the rotation attribute will cancel out a previous input in any one of the others. Rotations involving groups can affect the size, the change seems to follow the changing boundary box. Components seem to be more stable, but again misbehave when more than one axis is considered, Despite the updates in Ruby there seems to be little done to fix these bugs, however there are workarounds to achieve the results you require. The first important point, I would like you accept is that all onclicks need to be on the same level of nesting, there's no point placing an onclick event in a lower nesting than the other. I generally use nested groups only for parts of an object, like an "I beam" made of top flange, web and bottom flange. Then the object (I beam), the sum of its parts, is then a component. Collections of components may be then held in a group. So the second is that using dynamic groups can be more problematic, unless they are simple So any animated object(s) should be a component and it is better to nest animated component(s) within another component, otherwise the rotation formula can be overridden when swapped or inserted. At this point you may need to understand why attributes can be overridden, if they were not, then swapping a mouse with a elephant would mean their sizes would always match, etc. However you can match them, if the values are passed one level down and "current" is used in the parent if you want to, say have beam lengths to always match after a swap. I am still trying to rationalise DCs intricacies myself. so most times I plug in data / methods until it works Anyway, feel free to add any more problems, then can add some more observations

Really incredible what can be done with this tool. I miss some links to architectural projects though, -partially or completely done with SU. Nick Sonder is one good example. What about bigger projects, - anyone?

D*** you are good! Thank you pcmoore. Works great! I will study this.

I have a similar inquiry. Probably would lead to the same thing though. I built a vault door for a bank (it's old school), but it also has a small glass door in the inside of it that opens to adjust the mechanics. Was wondering if it's possible to be able to open the glass door on the back, even though it's nested under the same component as the vault door too. So far I've tried assigning attributes to parts of the vault door, so if you click a piece of the vault door, it rotates the whole thing, but haven't had any luck with that. But if I assign the attribute the whole component, I can't get the glass door to open. Anyone have any clues? I'm very much a noob at this!

Sorry my bad, should have said spin port not spin wheel, which may have confused you. You have tried it the other way round, you should wrap the component with the animation in another then change this new component to the same axis. So with your original, select the spinport and the guide and make this a component, then right click change axis, (hide rest of model) and place the rotation is in reference to the parent environment, so the wrapper acts as a shield or bridge between the two axes or worlds

Personally I'm not a fan of the trays either. However it is possible to create separate trays and position them as you want. For example I have a permanent floating tray with only Entity Info.

You're getting the snapping to an apparent grid because that's what you have it set to do. Untick Grid Snap and it won't do that. [image: wAuU_2013-10-29_06-40-30.png] If you want to adjust the viewport size without adjusting the size of the model, tick the box for Preserve scale on resize. Leave it ticked for that viewport or it will resize when you untick it. [image: 70oA_2013-10-29_06-41-34.png]

Hi By placing a component with hole cut both sides and a rim within a component wrapper one can place the door then explode the first wrapper which in turn activates both hole cutters attached solution which works after exploding, moreover have a look at the window opening for double leaf in my spot on the warehouse (pcmoor) updated opening to have size options cheers Philip insert bottom left, right click, explode

@daredevil said: @unknownuser said: Anyone dare the challenge? DC challenge ? I'm here !! If I have some time to spend on it, I will try next days... Did you have more info about this kind of window ? I think there is a rail to connect the top end of the window to the fixed frame, but not in your model... Yes, -you are right Didier, I just did not model it Attached is an updated version with the track hinge The window should be correctly placed in the horizontal position now, -but out of place in the two other positions. See photo If you look close you can imagine the L-fitting and track marked on this photo. [image: FSLR_IMAG1074.jpg] Updated version

Hi Jim, Thank you for a very nice Christmas gift! Been struggeling with this for a while now. ..I was close but missed on this part; =Parent!HevSenk+67.64 Thank you again and have a Merry Christmas to you and your family. Merry Christmas also to all followers in this thread!! @jim said: You will have better luck working outside-in, or top-down. Put the onClick animation at the highest logical level, and pass the animation attribute down to any components that need it. Attributes can only be "seen" by direct parents or children, so if you have more levels of components that need access to the animation attribute, you need to reference the attribute at each level. ` Top-Level Component OnClick(animate("anim", 0, 100) anim: 0 Child-Component anim: =Parent!anim Child-of-Child-Component anim: =Parent!anim`