All right - Flame away on this:
^C^C._-purge;_all;*;_no;._-purge;_regapps;*;_no;._zoom;_extents;._-layer;_set;0;;._audit;yes;._-overkill;all;;done;
All right - Flame away on this:
^C^C._-purge;_all;*;_no;._-purge;_regapps;*;_no;._zoom;_extents;._-layer;_set;0;;._audit;yes;._-overkill;all;;done;
Charles Shade LT 2013
www.cshadedesign.com
That is entirely a matter of personal preference... One that is as unimportant as writing a script (.SCR) in a single line, or multiple lines (where <Enter> and spaces are required).
To that end, those that use full-AutoCAD in lieu of LT can even use LISP code in the macro if they so choose. So you've effectively suggested that we all choose to relegate ourselves to one of multiple methods of writing a macro, and one that doesn't support *error* handling (again for those with full-AutoCAD)... Not exactly 'best practice'.
Just know that what you've just suggested is a rigid departure from what is considered 'coding best practice' in every other AutoCAD programming interface (i.e., LISP, .NET, and ObjectARX APIs)... For example, consider the code being called by your 'no spaces' macro using Reflector, or IlSpy, or look at the developer documentation.
"Potential has a shelf life." - Margaret Atwood
I wonder if the OP knew his query would need such detailed explanations?
The Lisp and other programming language abilities are of interest but completely mute in an LT Forum area.
There is little chance that the OP or anyone using LT can use that programming unless they are in violation of the EULA with third party software.
Charles Shade LT 2013
www.cshadedesign.com
AFAIK, the OP's query was answered back on the first page, and the 'detailed explanations' were in direct response to specific comments by other members.
Perhaps a better place for this thread is the AutoCAD Customization Forum, given the specificity of the request from the OP.
I too started out using LT, and know full well that it's easy to put on 'LT blinders' when making blanket statements that are, in the bigger picture, naive.
Respectfully, I do not recall posting any LISP code, beyond the 'setvar' snippet here, and have only otherwise mentioned them (LISP and other programming languages) to add clarity following another member's naive statements.
"Potential has a shelf life." - Margaret Atwood
You're killin' me here.
Charles Shade LT 2013
www.cshadedesign.com