I have been trying to purge layers on autocad mac. I have been entering the command PU (purge), then I select LA (layers), then I type in the layer name. Then I am prompted to select yes or no to verify the layer to purge. Whether I select yes or no, I end up at the empty Command prompt and still have my unwanted layers. Suggestions?
I'm not a mac guy, but possibly some block definitions using the unwanted layers..
Try the laymrg command to merge those layers with layer 0.
HTH
Henrique
@patsyrwhatley wrote:
There is no laymrg command. There is a merge command.
Sorry, but as I said before, "I'm not a mac guy"
From the Help files:
I thought that the command existed in MAC...
Henrique
According to this link, there is no laymrg command.
http://www.autodesk.com/products/autocad/compare/compare-platforms
Perhaps it is because it is an arx implemented command.
I have no suggestions for the OP. It's a pity that the Mac version is somewhat crippled. If you have a dual boot capability perhaps you could boot into a Windows shell and run autocad there.
Hi dbroad,
thank you for the link.
Reading that article I realize that there are more commands in the AutoCAD for Mac help files, that actually are not available...
The AutoCAD 2014 for MAC Help should be revised...
Thank you.
Henrique
@dbroad3 wrote:According to this link, there is no laymrg command.
http://www.autodesk.com/products/autocad/compare/compare-platforms
Perhaps it is because it is an arx implemented command.
I have no suggestions for the OP. It's a pity that the Mac version is somewhat crippled. If you have a dual boot capability perhaps you could boot into a Windows shell and run autocad there.
I knew .NET wouldn't work on Mac (I use Mac at home, not for CAD) as that is relegated to Win OS, however I could have sworn I read that ObjectARX (C++ for AutoCAD) would work, given Cocoa (C++ for Mac) on OSX. *not sure*
In any event, this can all be done via AutoLISP; it will just take longer to process, store the applicable data, and may require multiple Command calls due to lack of ActiveX support for Visual LISP.
Cheers
"How we think determines what we do, and what we do determines what we get."