4/18/2023 0 Comments Autocad copyclip![]() ![]() , 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. 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. Sometimes both- I have Engineers who don't do ANY 3D. They really work together as an effective way to manage the growth of your design assembly, 2D OR 3D. Good luck with your modeling using BOTH Blocks and Groups. 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 ! 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) ! ![]() 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'll insert as hard (unexploded) blocks, those subassemblies and components. 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. AND lets say that some of those subassemblies are still "growing" themselves. Lets say that some of those parts are really sub-assemblies themselves, and so now your part count is really starting to grow. Lets say you build your assembly and its getting a bit complex as your part count increases. Now here's where it begins to get pretty cool. The added feature of file size really comes into play when your assembly begins to grow in part count. AND it allows you to group your objects in a similar manner as groups, without giving up the ability to edit them as needed. There's nothing "majic" about exploding blocks and increasing file sizes.Īs to editing blocks in place- yes. The entities were intended to be individual elements of the new file in the 1st place. The block was only a mechanism to bring your group into the new file. Fee RE: copy and paste grouped objects PMR06 (Structural) 14 Mar 08 12:30Įxploding blocks ABSOLUTELY increases file size. You might get unwanted entities in a window, and collecting the previous entities from an exploded block is just too easy. I might mod it to explode last (the inserted block), and eliminate selecting in the window. ![]() 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 Frequently use groups to manage both 2D & 3D entities for the exact purpose of the initial post. I get alot of success out of this approach. (I'm going to try the macro, and modify it with the prev. (remember to set your pickstyle to 1 afterward.) Its entities are retained as the previous selection set. (I use block with the retain as a block box checked). I get around the original problem in this manner: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |