tails Posted December 15, 2010 Share Posted December 15, 2010 Hi, I done this once a while ago but somethings gone wrong. How do I "explode" the orange box around the drawing. I'm importing a DWG from a client and need to make changes but the drawing has an orange box I have to click on/through to get to elements of the drawing. I'd like to explode this ? Thanks for your time. Quote Link to comment
mike m oz Posted December 15, 2010 Share Posted December 15, 2010 Your DWG is probably a symbol. Make sure you are at the top level (ie. no orange border visible). If you can see that it is a symbol on the OIP then use Convert to Group on the Modify menu to "explode" it. Note if your symbol contains 2D and 3D information then you need to do this twice in order to get all of the information: - In Top/Plan View copy the symbol. Then convert it to a group to get the 2D parts. - Switch to Top View and paste in Place the symbol again. Then convert it to a group to get the 3D parts. - Select both groups and ungroup them. The reason for this is: - When you convert a symbol to a group in a 2D view (ie. Top/Plan View) you lose the 3D components; and - When you convert a symbol to a group in a 3D view you lose the 2D components. Quote Link to comment
tails Posted December 15, 2010 Author Share Posted December 15, 2010 Thanks Mike, that seems to have worked I'll investigate further, as VW has just quit on me. Quote Link to comment
tails Posted December 15, 2010 Author Share Posted December 15, 2010 Yay! So I have done as you have said, but imported only the 2D elements as I only work in 2D at the moment. I then ungroup it and that gives me all the separate elements for me to delate and move around, without the orange box. Quote Link to comment
tails Posted December 15, 2010 Author Share Posted December 15, 2010 Unfortunately it has just quit again, never known a mac quit programs as much as this one both VW and sketchup. Sigh! Quote Link to comment
RubenH Posted December 15, 2010 Share Posted December 15, 2010 The problem (quit) Tails is that Vectorworks 2008 isn't fully compatible with Snow Leopard, since Snow came after Vectorworks 2009. http://kbase.vectorworks.net/questions/712/Vectorworks++%26+Mac+OS+X+Snow+Leopard+V+10.6 Quote Link to comment
tails Posted December 16, 2010 Author Share Posted December 16, 2010 Thanks Mr Gog, I think the mac I have here runs leopard not snow leopard. Plus it has worked numerous times before. i'll see if it works today as if not I'm in a bit of a pickle! Quote Link to comment
tails Posted December 16, 2010 Author Share Posted December 16, 2010 Sorry I'm wrong I have 10.6.5 so that is snow leopard, still it has been working. Quote Link to comment
tails Posted December 16, 2010 Author Share Posted December 16, 2010 Does the following mean anything to anyone? I can copy the rest but it's rather long. Process: VectorWorks [3757] Path: /Applications/VectorWorks 2008/VectorWorks 2008.app/Contents/MacOS/VectorWorks Identifier: net.nemetschek.vectorworks Version: 13.0.0 (76681) (???) Code Type: X86 (Native) Parent Process: launchd [114] Date/Time: 2010-12-16 12:03:46.138 +0000 OS Version: Mac OS X 10.6.5 (10H574) Report Version: 6 Interval Since Last Report: 72480 sec Crashes Since Last Report: 4 Per-App Interval Since Last Report: 9501 sec Per-App Crashes Since Last Report: 4 Anonymous UUID: 89E6B966-22D7-4B40-98D0-3E8156544229 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffffffff Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 net.nemetschek.vectorworks 0x004b501b start + 4923875 1 net.nemetschek.vectorworks 0x004c0079 start + 4969025 2 net.nemetschek.vectorworks 0x004b6e8c start + 4931668 3 net.nemetschek.vectorworks 0x004b701b start + 4932067 4 net.nemetschek.vectorworks 0x004be7f8 start + 4962752 5 net.nemetschek.vectorworks 0x004beb64 start + 4963628 6 net.nemetschek.vectorworks 0x002ab167 start + 2786095 7 net.nemetschek.vectorworks 0x001a3ff5 start + 1708477 8 net.nemetschek.vectorworks 0x000510a0 start + 320104 9 net.nemetschek.vectorworks 0x000ba40d start + 751061 10 net.nemetschek.vectorworks 0x000c95cc start + 812948 11 net.nemetschek.vectorworks 0x0005b86b start + 363059 12 net.nemetschek.vectorworks 0x000b394b start + 723731 13 net.nemetschek.vectorworks 0x000b325e start + 721958 14 net.nemetschek.vectorworks 0x0005b2fb start + 361667 15 net.nemetschek.vectorworks 0x00002f3a start + 258 16 net.nemetschek.vectorworks 0x00002e61 start + 41 Quote Link to comment
islandmon Posted December 16, 2010 Share Posted December 16, 2010 As the OS evolves, various legacy Libs/functions are dropped into the ditch. Calls to those Libs/functions by older noncompliant untested apps often result in process crashes; this is not always the case ... sometimes tools just refuse to work properly. In fact, it is amazing just how long some VW versions can endure code collapse. It sure would be great there was such a thing as a self-healing app. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.