copy and paste grouped objects 1

[hngopal]

Hello world,
(sorry cudnt resist)

I am using ACAD-LT2000. I frequently need to group objects in my assemblies to check individual part movement. 'group' and 'move' works fine for me.

The problem arises when I need to use grouped parts from one file in a different file. (common parts, different assy.)

1. When I copy-paste, the grouping does not remain. I will have to select every object again to group and move it.

2.If I convert it into a block, I loose the flexibility of changing the vertex position of some of the objects in case the part fouls. (I can use explode, but then I end up with earlier problem)

So, I would like to transfer grouped entities from one file to another,
a. without losing the flexibility of changing individual vertices
b. having to ungroup and group every time.

Any solutions?
Thanks

- H

 

[Exxit]

Hello hngopal,

the answer is Yes & No!

You can't copy and paste a group. The objects in the group are saved in the data. If you copy, you get new objects, so the group can not excist anymore...

Workarounds:
1st. I would use blocks. I never use groups.
2nd. for the group-fans: Use the xref command -> bind -> insert -> explode the blockreference...

Lothar

ADT 2004

 

[dimjim]

Why not insert it on a unique layer and then you can
easily reblock very easily or move it by turning
only that layer on and capturing everything.

 

[PMR06]

Do you know how to create custom buttons? If so, I use the following macro. It's kind of cumbersome, but if you are hooked on groups, it helps.

^C^Cpasteclip;\-group;create;*;;\\;

From one drawing you copyclip whatever group you want. Then in the other drawing click this button. The first pick point \ is where the group will be pasted. The next two pick points \\ will be crossing or window to select what you just pasted and add them to a new, unnamed group. FYI: When you pasteclip, those objects pasted are not added to the previous selection set... which would have been nice to eliminate the reselecting.

 

[Exxit]

@PMR06,

BTN,

L.

ADT 2004

 

[cfee]

I like the macro posted by PMR06.

I get around the original problem in this manner:

Select the group. Make an internal block. (I use block with the retain as a block box checked) . Copyclip the block. Yes, I know, but stay with me a minute.

Paste it into the receiving drawing. Explode it. Its entities are retained as the previous selection set. Remake them into a group. (remember to set your pickstyle to 1 afterward...)

(I'm going to try the macro, and modify it with the prev. paragraph in mind !)

I get alot of success out of this approach. I Frequently use groups to manage both 2D & 3D entities for the exact purpose of the initial post. X-Refs are a marginal approach at best for this particular need (in my never to be considered humble opinion (!)) I'm going to try the macro. I might mod it to explode last (the inserted block), and eliminate selecting in the window. You might get unwanted entities in a window, and collecting the previous entities from an exploded block is just too easy. But the macro idea's pretty cool !

Good luck-

C. Fee

 

[PMR06]

cfee,

I never considered creating a block, etc. Keep us posted on that macro. I'd love to get rid of the reselecting step if possible!

 

[Exxit]

Maybe this macro:
Block into group

^C^C_pasteclip;\_explode;_last;_-group;_create;*;;_previous;;

ADT 2004

 

[IFRs]

If you use a block and a component needs to be moved within the block, I use refedit to edit the block in place. Would this work for you? If you enable grips within blocks you can move entities within the block directly,

 

[hngopal]

Thanks a bunch ppl.

I'm a newbie and dimjim's soln sounds simplest to me. But can anyone shed light on the effect on file size by creating too many layers?

I will definitely play around with the other options suggested. I was not even aware of the 'refedit' and macros, I have never attempted before. This is my chance.

- H

 

[IFRs]

Exploding blocks will increase the file size if the block is used more than once.

 

[cfee]

Exploding blocks ABSOLUTELY increases file size. But consider-

The block was only a mechanism to bring your group into the new file. The entities were intended to be individual elements of the new file in the 1st place. There's nothing "majic" about exploding blocks and increasing file sizes.

As to editing blocks in place- yes. I've found ALOT of value in this. AND it allows you to group your objects in a similar manner as groups, without giving up the ability to edit them as needed. The added feature of file size really comes into play when your assembly begins to grow in part count. Now here's where it begins to get pretty cool-

Lets say you build your assembly and its getting a bit complex as your part count increases. Lets say that some of those parts are really sub-assemblies themselves, and so now your part count is really starting to grow. AND lets say that some of those subassemblies are still "growing" themselves...

So- Inserting them as X-refs might take on some interest here, and may be where the value begins to creep in, but I've found it a bit cumbersome to add the extra management layer of X-Refs to my already complex task of creating the assemlbly and managing its growth in the 1st place. So-

I'll insert as hard (unexploded) blocks, those subassemblies and components. I'll GROUP them as appropriate, keep file sizes down (as far as I'm able) by not exploding where possible, GROUP them as operating sub-systems for the assembling and ANIMATING of my assembly, and LET MY DESIGNERS CONTINUE TO WORK on the components and sub-asseblies, as I manage the integrity of the top assembly. I can make internal edits where necessary, my people are working unhindered on their portions, Blocks are nested and managed effectively, and operating sub-systems are GROUPED in the top assembly where appropriate, and this thread is maintained all the way down to the individual component, WHOEVER is working on it, with updates continuing along by REINSERTION, _ONLY_ when aappropriate, and not necessarily at every start up (as with X-Refs) !

The macro's cool, and works as advertised ! I like the one posted just above ! I suppose I should have considered something of the sort some time ago, but you know how it goes- you get into a flow, and sometimes interesting new ideas come along as you progress !

Good luck with your modeling using BOTH Blocks and Groups. They really work together as an effective way to manage the growth of your design assembly, 2D OR 3D.

Sometimes both- I have Engineers who don't do ANY 3D. They LOVE laying out their ideas, grouping and blocking as above, and with the help of a capable design staff, group and block and animate and motion-study, etc. , working out issues as their engineered product progresses, working closely with Design staff, who work back and forth in both directions (Engineer-Designer-Detailer-Designer-Engineer...) in a really dynamic design environment. The integrity of the engineered design is thus maintained, and prototype iteration is kept to an ABSOLUTE minimum, keeping design cycles short, making design-to-market shorter, and increasing quality of the delivered product, thus enhancing comapy revenues, and getting everybody raises in the process !!! Who would have guessed ! Ok, I'm having a little fun with it, but you get my point .

Post back with progress? I think there's a group of us who are interested in how this is going for you, and getting some interesting ideas from each other in the process !

Good luck-

C.Fee

 

[Exxit]

Refedit is not a command in LT...

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2880695&linkID=9240817

L.

ADT 2004