topic Re: Deconstruct library parts in Libraries & objects

Deconstruct library parts

KeesW — Tue, 31 Jul 2007 07:43:26 GMT

Is this for the wish list?

I've created a desk with complicated drawers and some divisions out of slabs and walls. I converted it into a library object and used it on the floor plan. Now, I want to alter it.

Can we explode it, or deconstruct it, to convert the object back into its elements - eg walls, slabs, etc?

I usually save the objects that I design before converting them into library objects - but in this case, I didn't.

Re: Deconstruct library parts

TomWaltz — Tue, 31 Jul 2007 09:40:56 GMT

It would be really nice... but I'm afraid that's one for the wishlist.

Re: Deconstruct library parts

Rob — Tue, 31 Jul 2007 11:46:01 GMT

just a little bit more on that as I have seen this type of question on this forum few times before...
the actual tools (eg walls,slabs,beams,roofs etc) do not have an exact representation in GDL language so eg a slab could be actually coded by various types of PRISM command in GDL etc. Therefore it is impossible to do a assemble-disassemble action.
In other words the tools are just an interface to various GDL commands for each tool... if it makes a sense.

Re: Deconstruct library parts

Djordje — Tue, 31 Jul 2007 17:11:10 GMT

TomWaltz wrote:
It would be really nice... but I'm afraid that's one for the wishlist.

... something on the line of SketchUp component editing in place?

Let's wish ...

Re: Deconstruct library parts

TomWaltz — Tue, 31 Jul 2007 18:25:21 GMT

Djordje wrote:
TomWaltz wrote:
It would be really nice... but I'm afraid that's one for the wishlist.
... something on the line of SketchUp component editing in place?

Let's wish ...

That would be nice!

Re: Deconstruct library parts

Ignacio Azpiazu — Wed, 01 Aug 2007 02:14:33 GMT

KeesW wrote:
I've created a desk with complicated drawers […] Now, I want to alter it.

That is the reason why it often makes a lot of sense to use modules for custom pieces of furniture and equipment --you open the module, edit and save with the same name or a new name, and that's it. That and the fact that because you can use layers you have a lot more control over how the thing looks and performs in different views. You can put annotations to show in some equipment plan, do a fancy 2d plan view and keep the model in a 3D-view-only layer, you can even have the roof vent moving around in the roof plan following your equipment or whatever. With the basic shapes and grills and special operations and profiles you can do a lot, and the module can include some slabby object for some handle or whatever too.

I know it is too late for this one but it will save a lot of time and look great the next time.

Re: Deconstruct library parts

Laura Yanoviak — Wed, 01 Aug 2007 15:28:06 GMT

Ignacio wrote:
That is the reason why it often makes a lot of sense to use modules for custom pieces of furniture and equipment --you open the module, edit and save with the same name or a new name, and that's it. That and the fact that because you can use layers you have a lot more control over how the thing looks and performs in different views. You can put annotations to show in some equipment plan, do a fancy 2d plan view and keep the model in a 3D-view-only layer, you can even have the roof vent moving around in the roof plan following your equipment or whatever. With the basic shapes and grills and special operations and profiles you can do a lot, and the module can include some slabby object for some handle or whatever too.

This is a fantastic tip (although it almost seems obvious...)!

Re: Deconstruct library parts

Rob — Wed, 01 Aug 2007 22:40:25 GMT

Ignacio,

that's a fantastic tip...definitely I have to explore this approach a bit more...thanks

Re: Deconstruct library parts

Ignacio Azpiazu — Thu, 02 Aug 2007 00:19:39 GMT

Still another advantage I forgot to mention, that draws ooohs and aaahs: because you are composing your piece of equipment with different tools and objects, you can also set different display settings for each component story-wise. So that as you move your module you are moving vertically-coordinated stuff that displays on the floor(s) above and/or below (some all stories up, some immediately above, some others below), without actually seeing those components in the 'home story'.