Module files

[Tom Krowka]

I have selected several drawing elements and saved them as a module. When I open the module, I see have all the layers, layer combinations, etc. of the drawing I saved it out of.

Is there I way I can save a stripped down version of that module that will have only the layers of the elements that I saved, and the layer combination that was used at the time?

That way when I insert it into a different drawing, it won't bring all the extra layers with it.

[Anonymous]

And another question...

I see that there is supposed to be a 2DL extension. It sounds to me like this would be the perfect format for simple 2D details -- small and easy. However, there is no way that I can find to save to this format. What am I missing? Is this worth pursuing?

[Karl Ottenstein]

TomWaltz wrote:
We have one PLN with many stories, and place what would have been a single MOD file on each story. A whole folder full of MOD files is now all in one PLN.

The performance diffference was minimal, and the end result was far more predictable.

The only downside is that instead of using the "Save selection as module" commands, you have to cut/paste from one file to the other, then create a new hotlink yourself.

Isn't it easier to just create a view set with views for each module, and use Publisher to create all MOD files in one step?

Karl

[Karl Ottenstein]

Jay wrote:
And another question...

I see that there is supposed to be a 2DL extension. It sounds to me like this would be the perfect format for simple 2D details -- small and easy. However, there is no way that I can find to save to this format. What am I missing? Is this worth pursuing?

Actually, MOD is small and easy (too). Just create a Publisher set for the 2D details and publish them to MOD files for use elsewhere.

Karl

[TomWaltz]

Karl wrote:

TomWaltz wrote:
We have one PLN with many stories, and place what would have been a single MOD file on each story. A whole folder full of MOD files is now all in one PLN.

The performance diffference was minimal, and the end result was far more predictable.

The only downside is that instead of using the "Save selection as module" commands, you have to cut/paste from one file to the other, then create a new hotlink yourself.

Isn't it easier to just create a view set with views for each module, and use Publisher to create all MOD files in one step?

Karl

I'm not sure WHAT I was trying to say back then, but yes, a single PLN publishing to MOD is what we're doing now.

[Anonymous]

Karl wrote:

Jay wrote:
And another question...

I see that there is supposed to be a 2DL extension. It sounds to me like this would be the perfect format for simple 2D details -- small and easy. However, there is no way that I can find to save to this format. What am I missing? Is this worth pursuing?

Actually, MOD is small and easy (too). Just create a Publisher set for the 2D details and publish them to MOD files for use elsewhere.

But does it really elliminate ALL unused layers/linetypes/etc.? That's where the confusion lies -- at least for me.

[Karl Ottenstein]

Jay wrote:
But does it really elliminate ALL unused layers/linetypes/etc.? That's where the confusion lies -- at least for me.

Yes (well, AFAIK) ... as Matthew and Tom say below ... a MOD files only contains the attributes for the elements contained in the file.

You can infer this relatively easily ... in Attribute Manager, select all and save as an AAT file. Then, select just a wall, say, and save selected as module. Granted very different file formats, but the AAT will be much bigger, even if you zip both.

Karl