Alisp

The AutoLisp Beginner
Welcome to the world of AutoLisp. Soon you will know what the hell a car of a cdr is.
Let's get to it. But how?
When I say "type this at the command line" I will put the actual key strokes in red except for the enter key. This will mean
that you should type the red letters in at the Command Prompt inside AutoCAD as if you were typing the command "Line".
To clarify, If I say "type this at the command line: Line and press the enter key, you would type the word "Line" at the
command prompt inside of AutoCAD and press the enter key afterwards. Got it? No? Oh, never mind. Just keep reading. I
won't leave you behind.
The first thing you should know about AutoLisp:
AutoLisp always has as many opens "(" as it does closes ")".
Every AutoLisp program should look similar to this:
(defun myProg()
(princ "Jeff")
(princ)
)
You can execute AutoLisp at the Command Prompt inside AutoCAD. This is where we will start.
AutoLisp is a language that returns a value after executing. Every function that executes will return or echo it's answer.
Let's test this. Open AutoCAD and type this at the command line: (+ 1 2) and press the enter key. (The + function adds
numbers together). Look at the command line. You should see something that looks like this:
Notice the 3 below the line you typed and the Command Prompt? AutoLisp returned the value of the function you typed in.
Try it again. This time change the 1 to 3 and the 2 to 5. As in (+ 3 5). What did it return? AutoLisp ALWAYS returns the
answer.
Variables
-1-
What the hell is a variable? Variables are names or placeholders if you will, for values. Remember algebra? (Your going
to wish you would have paid attention to Mrs. Johnson instead of that cheerleader on the first row with the blond hair and the
big...well ...nevermind.) X=1 Y=2. Look familiar? X and Y are variables. They could mean anything. If you need to store
data, such as a string or integer, you will need to assign a variable name to the data. The way to do this is to use the setq
function. Ex. (setq a 1). This set's the variable a to the value 1. Anytime you use the variable a in your program, it will
actually use the value 1. If you typed (+ a 2) and pressed enter, AutoLisp would return 3.
You can use any variable name you want. (Practically) Upper case and lower case does not matter. I would suggest you do
not use any names that AutoCAD has in use. How do you know which ones are being used by AutoCAD? Good question
Jeff. The simplest method to find out if AutoCAD is using a name is to type in the name at the Command Prompt inside of
AutoCAD and press the enter key. If nothing happens, use it.
If you were to write a program named Line.lsp and load the program, AutoCAD's built in LINE command will seem to be
replaced. When you type Line you will run your program instead of the Line command. You will get the built in functions
back next time you open a new drawing or you could use a period in front of the command to make it execute an AutoCAD
built in function. Ex. .LINE would execute the AutoCAD built in function instead of your program. I do not suggest toying
with this.
Name your variables and programs something unique. AutoCAD does not have any "built in" functions that are a single
character. So a through z are fair game. ( Unless they are assigned in the programs that automatically load during startup
such as the ACAD.lsp, ACADDOC.lsp, and ACAD.PGP files. Better check your variable names at the command line as
discussed earlier. Also, the letter T is used by autolisp as a TRUE symbol.)
[ Thanks Ethan! ]
Some safe examples of variable names are:
(setq a 1)
(setq b1 3)
(setq aa1 4)
(setq jeffsVarForHisProgram 1)
(setq thisVarA 2)
Some bad examples are:
(setq line 1)
(setq acad 4)
(setq ltscale 7)
(setq car 12)
(setq cdr 400)
Again with the car and cdr stuff? What is it man?
I suggest you use variable names that are somewhat descriptive. If you had to name a variable for a string that contains
people's names then I would use something like this (setq strName "Jeff").
-2-
If you have a variable name for a integer that holds the data for a value that represents a title block selection then I would
use something like this (setq intTBSelection 3).
A couple of important last minute things:
While inside AutoCAD you can check your variables to see what they are set to. This is very handy when debugging a
program. Type (setq aa1 454) and press enter. To check the value of the variable we just declared, simply type !aa1 at
the command prompt. Go ahead. Try it. AutoLisp echo's the value to the command line. Using an exclamation point in
front of the variable prints the value of the variable to the command line.
New! Have you ever seen an AutoLisp program crash? Ever try to debug it? It looks like a bunch of garbled mess. How
in the heck can you cipher through all of this:
It's not as tough as it looks. You only have to worry about the first or second lines returned. In this case the culprit that
crashed the program is (+ CANT 1). Let's look at the variable CANT. At the command prompt type !CANT<enter> It will
return nil. You can't add nil to 1. Why is CANT set to nil? Let's look at the next line. (SETQ CNT(+ CANT 1)) This
looks like a counter of some type. I'll bet the variable name CANT should have been CNT. A typo! At this point I would
open the program with NotePad and search for the text string CANT. If this is the only place it shows up then my first
explanation would be correct. I would retype the CANT variable to be CNT. Save the program and try it again.
Okay, enough for variables for now. Let's move on.
Functions
Let's take it a step further and create our very own function. Every defined function begins with the declaration defun.
Ex. (defun myProg() or (defun C:myProg()
The difference between using the C: and not using the C: will be explained later. For now. let's learn another AutoLisp
function to use in our first program. The function princ simply prints to the command line. Ex. (princ "Jeff") would print Jeff
on the command line. Alrighty then, let's type this at the command prompt:
(defun myProg()(princ "Jeff")) and press enter.
You should see something that looks like this:
-3-
Now type (myprog) at the command prompt and press the enter key. You should see something that looks like this:
The program executed and printed "Jeff" on the command line. Then the program echoed the last statement to the
command line. AutoLisp always returns the answer right? That is why you ended up with Jeff"Jeff" on the command line.
The way to get rid of the echo is to use a princ statement without any parameters as the last statement in your program. Ex.
(princ).
Let's rewrite the program using the (princ) function to stop the echo. Type this is in at the command prompt:
(defun myProg()(princ "Jeff")(princ))
Then type (myprog) and press enter. What happened? No echo. Cool.
Let's back track and explain the C: we mentioned earlier. The C: tells AutoCAD that you want this program to be executed
at the Command Prompt like a built in function. Let's redo our program. Type this at the command line:
(defun C:myProg()(princ "Sanders")(princ))
Now type (myprog) and press enter. What happened? Why did it print Jeff? We used the C: in front of the function. We
do not have to put the program inside of quotes to execute it. (There are some other differences, we will get to that in the
advanced levels.) To execute a function that was declared with a C: you only have to type the name of the program at the
command prompt. Let's do that now. Type myProg at the command prompt and press enter. It printed "Sanders" to the
command line. Wow! Don't rush off to show everyone yet. The next time you open a drawing your new function will
disappear and you will have to type it in again. Dang!
Wait! We could save it to disk and reload it whenever we needed it. Let's do that. I will assume you have a windows
operating system for the following instructions. Yes. I know what happens when you assume something. Let's not go there.
Click on the Start button. Go to Programs. Go to Accessories. Go to NotePad.
Notepad should open. When it does, type in:
(defun C:myProg()
(princ "Jeff")
(princ "Sanders")
(princ "AutoLisp")
(princ)
)
-4-
Now, go to the "File" drop down menu in NotePad and select "SaveAs". Type in myProg.lsp for the name of the program.
Wait! Don't hit the SAVE button yet. NotePad has a bad habit of assuming you want to save it as a text file with the
extension txt. Go to the "SAVE AS TYPE" drop down box and select "ALL FILES". Look at the top of NotePad in the "Save
in:" location. Make sure you save the file in a location where AutoCAD can find your file in it's search path. I suggest
creating a directory on your hard drive to keep all of your AutoLisp files in. I would suggest a directory such as :
"C:\ACAD\lsp". Change the "Save in: " location to point to this directory. Now press the SAVE button. Go back to
AutoCAD. Go to the "Tools" drop down menu and go to "Preferences". Click the "Files" tab. Click the + sign in front of
"Support File Search Path". Click the "ADD" button. Type in the directory you saved the "myProg" lisp file in. Ex.
"C:\ACAD\lsp" . Click the "APPLY" button. Click OK to the alert box. Click the OK button to exit the dialog box.
At the command prompt inside AutoCAD type (load "myProg") and press enter. Then type myprog and press enter. If
you hit the F2 button to bring up the text screen, you should see something that looks like this:
You have successfully created an AutoLisp program. Congratulations! One last thing about functions:
We discussed the defun() statement and what it meant. We did not discuss the open and close parenthesis "()" after the defun
statement. We will do that in the intermediate tutorial level. The point I wanted to get to here is, if you put your variable
names inside these parenthesis and after a / you will reset these variables to nothing...or nil as AutoLisp defines it. Therefore
the exclamation point before the variable name will return nil. This saves room in RAM and also keeps your program from
getting corrupted by other programs that do not reset the variables to nil. Always include the variables you use inside the
parenthesis after debugging your program.
An example of this is (defun C:myProg(/ varA varB varC).
You are so, so, close to uncovering the mysteries surrounding the car and cdr quandaries. Move on to the next level.
LEVEL 2
The AutoLisp Intermediate Tutorial
Welcome to the Intermediate Tutorial. You know the beginners steps to writing an AutoLisp program. You don't? See the
Beginner's Tutorial. Now all you need to know is what to write. What functions are available? How do you manipulate
entities inside of AutoCAD? What the heck is a car of a cdr?
I believe that you not only need to know what a function returns if it is successful, but also what the function will return if it
fails. This will help you troubleshoot your programs. That is why I believe this will become the Ultimate AutoLisp Tutorial.
In the examples of the functions below, I've included the most common reasons why AutoLisp programs crash along with the
error message you will receive. Remember, when AutoLisp has an error, execution is aborted.
-5-
Let's begin with Data Types:
Data Types:
String
A string is an AutoLisp data type consisting of alphanumeric characters inside quotes.
eg. "Jeff" "Sanders" "1245r" "3"
Integers
An integer is a number without a decimal place.
eg. 1 23 456 67890 -5 -687
Real
A real number is a number that has a decimal place.
eg. 1.0 23.034 456.2 -56.345
List
A list is an AutoLisp data type that has parenthesis around it. Multiple data types can reside inside one list. This will also
unravel the mystery behind the car and the cdr.
eg. (1 2 3) ("Jeff" 156.0 45.0 3 "Sanders") (1) () ( (1 2 3) (4 5 6)("A" "B" "C") )
Variables or Symbols
We covered these in the Beginner's Tutorial. A variable is a symbol that is created by you, the user. eg. (setq a 1) (setq
pt1(getpoint "\n Select Point: ")) - a and pt1 are the variables.
Associated List
An associated list is a list that has a value associated with it. The assocation and the data are seperated by a period. eg. (1 .
455) (34 . "Sanders") You can find "Sanders" by looking up group code 34. We will get more into this when we take a look
at the DXF Group Codes later in this Tutorial.
Let's get started with the basic functions. Remember, you don't need to know all of this. You don't need to memorize all of
this. This is a reference. There will be no test. It will help you to read through it once to see what functions are available.
When you are writing a program and get stuck, come back here to find the correct function to solve your problem. Put down
your pencil. Really.... no test.
String Functions substr strlen strcase strcat
Number Functions abs atof atoi fix float itoa
-6-
List Functions car cdr cadr caddr caar cddr foreach list cons nth
Group Codes/Associated List assoc Entity_DXF_Group_Codes
Conversion Functions fix float itoa atoi atof rtos angtos
Math Functions + - * / +1 -1 cos atan sin sqrt expt
Selecting Entities entsel ssget
Selection Set Functions ssadd ssdel sslength ssname
Entity Functions entget entlast entnext entdel entmod entupd
File Functions open close read-line write-line New!
DXF Group Code Table
String Functions
Functions - substr strcase strlen strcat Example Programs
substr - This function retrieves part of a string.
Syntax : (substr "string" startPoint numberOfCharacters)
"string" - any valid string or variable representing a string. If you use a variable name omit the quotes.
startPoint - an integer or variable representing an integer that corresponds to the position in the stringto
start the substring at. The first character is character 1.
numberOfCharacters - an integer or variable representing an integer that corresponds to the length of

string to return. Length being the number of characters.
Returns a partial string starting at the character represented by startPoint and ending at the character
represented by the numberOfCharacters or the end of the string. Whichever comes first..
(substr "Jeff Sanders" 1 6) would return "Jeff S"
(substr "Jeff Sanders" 6 3) would return "San"
-7-
(substr "Jeff Sanders" 64 456) would return ""
(substr "Jeff Sanders" -4 3) would return "Error: Bad argument" [No negative character
positions]
(substr "Jeff Sanders" 4 -3) would return "Error: Bad argument" [No negative string lengths]
(substr "Jeff" 6 4) would return ""
(substr "" 9 3) would return ""
(substr "Jeff Sanders" 9) would return "ders"
If you omit the last parameter, the remainder of the string from the startPoint will be returned..
strcase - This function converts to upper or lower case.
Syntax : (strcase "string" flag)
"string" - any valid string or variable representing a string. If you use a variable omit the quotes.
flag - a flag that sets uppercase or lowercase.
flag = T or nil
T = True nil = False
T = LowerCase nil or empty = UpperCase
Returns a string that is either upper or lower case depending on the flag setting.
(strcase "Jeff" T) returns "jeff"
(strcase "Jeff" nil) returns "JEFF"
(strcase "123a" nil) returns "123A"
(strcase "" nil) returns ""
(strcase 123 T) returns "Error: Bad Argument Type" [123 is an integer, not a string]
(strcase 1.0 nil) returns "Error: Bad Argument Type" [1.0 is a real number, not a string]
(strcase "Jeff") returns "JEFF"
Omitting the flag is the same as having the flag set to nil or false.
-8-
strlen - This function returns the length of a string in characters.
Syntax : (strlen "string")
Returns an integer that represents the length of the string. The length is the number of characters.
(strlen "Jeff") returns 4
(strlen "Jeff Sanders") returns 12
(strlen "") returns 0
(strlen 123) returns "Error: Bad Argument Type [123 is an integer, not a string]
(strlen 1.0) returns "Error: Bad Argument Type [1.0 is a real number, not a string]
(strlen (list 1.0 2.0)) returns "Error: Bad Argument Type [(list 1.0 2.0) is a list, not a string]
strcat - This function adds multiple strings together to form one string.
Syntax : (strcat "string1" "string2" "string3" ....ect. )
"string1" - any valid string or variable representing a string. If you use a variable omit the quotes.
Returns a string that includes all of the strings in the list.
(strcat "Jeff" "Sanders") returns "JeffSanders"
(strcat "Jeff " "Sanders") returns "Jeff Sanders"
(strcat "" "56" "Jeff" "abcdefg") returns "56Jeffabcdefg"
(strcat "" 5 "Jeff") returns "Error: Bad argument type". [5 is an integer, not a string]
(strcat "" 3.1 "Jeff") returns "Error: Bad argument type". [3.1 is a real number, not a string]
This function can only accept strings or a variable representing a string as it's arguments. (parameters)
End of String Functions
Example Program 1:
(defun C:myProg()
(setq str1 "Jeffery")
-9-
(setq str2 "P")
(setq str4(substr str1 1 4)) ;sets str4 to 1st 4 characters of str1
(princ str4) ;Prints "Jeff" to the command line.
(setq str4(strcase str4)) ;Sets str4 to uppercase
(princ str4) ;Prints "JEFF" to the command line.
(setq int1(strlen str4)) ;Sets int1 to 4 (length of string)
(princ int1) ;Prints 4 to the command line.
(setq str5 (strcat str4 " " str2)) ;sets str5 to "JEFF P"
(princ str5) ;Prints "JEFF P" to the command line.
(princ) ;clean exit (supresses echo)
) ;close the program
Command: (load "myProg")<enter>
Command: myProg<enter>
Command: JeffJEFF4JEFF P
Program Example 2:
(defun C:NameMix()
(setq strName(getstring T "\n Enter your name: "))
(setq keepGoing 1)
(while (<= keepGoing (strlen strName))
(setq char1(substr strName 1 keepGoing))
(setq char1 (strcase char1))
(setq strName2(strcat char1 (substr strName (+ keepGoing 1))))
(setq keepGoing(+ keepGoing 1))
(princ (strcat "\n " strName2))
- 10 -
(princ "\n Program Complete.")
(princ)
Command: (load "namemix")<enter>
Command: namemix<enter>
Command: Enter Your Name: jeff<enter>
Command: Jeff
Command: JEff
Command: JEFf
Command: JEFF
Command: Program Complete.
Number Functions
abs atof atoi fix float itoa Example Program
abs - This function returns the absolute value of a number.
Syntax : (abs number)
number - any valid number.[integer or real number]
Returns an integer or a real number.
(abs 345) returns 345
(abs 345.5) returns 345.5
(abs -345) returns 345
(abs -345.5) returns 345.5
(abs "345JEFF") returns "Error: Bad Argument Type" ["345JEFF" is a string, not a number]
atoi - This function converts a string to a integer.
- 11 -
Syntax : (atoi "string")
Returns an integer.
(atoi "Jeff345") returns 0
(atoi "5") returns 5
(atoi "5.6") returns 5
(atoi "") returns 0
(atoi "345JEFF") returns 3
(atoi 5) returns "Error: Bad argument type". [5 is an integer, not a string]
(atoi 5.6) returns "Error: Bad argument type". [5.6 is a real number, not a string]
This function looks at the first character, then the next, then the next, ect. until it finds a character that
cannot be part of an integer.
itoa - This function converts an integer to a string.
Syntax : (itoa integer)
integer - Any valid integer.
Returns a string.
(itoa 345) returns "345"
(itoa 5.6) returns "Error: Bad argument type". [5.6 is a real number, not an integer]
(itoa "5") returns "Error: Bad argument type". ["5" is a string not an integer]
(itoa "345JEFF") returns "Error: Bad argument type". ["345JEFF" is a string, not an integer]
This function can only accept an integer or a variable representing an integer as it's parameter.
atof - This function converts a string to real.
Syntax : (atof "string")
Returns an real number.
- 12 -
(atof "Jeff345") returns 0.0
(atof "5") returns 5.0
(atof "5.6") returns 5.6
(atof "5'3-1/2"") returns 63.5
(atof "3-1/2"") returns 3.5
(atof "") returns 0.0
(atof "345JEFF") returns 345.0
(atof 345) returns "Error: Bad Argument Type" [345 is an integer, not a string]
(atof 3.4) returns "Error: Bad Argument Type" [345 is a real number, not a string]
(atof (list 3 4)) returns "Error: Bad Argument Type" [(list 3 4) is a list, not a string]
This function looks at the first character, then the next, then the next, ect. until it finds a character that
cannot be part of an real number.
fix - This function converts a real to an integer.
Syntax : (fix real)
real - Any valid real number.
Returns an integer.
(fix 345.0) returns 345
(fix 5.0) returns 5
(fix 5.6) returns 5
(fix "5.0") returns "Error: Bad Argument Type ["5.0" is a string, not a real number]
(fix "5") returns "Error: Bad Argument Type ["5" is a string, not a real number]
This function takes the whole number part of a decimal number and returns it as an integer.
float - This function takes a number (integer or real) and converts it to a real number.
Syntax : (float integer) (float real)
Integer - Any valid integer.
- 13 -
real - Any valid real number.
(float 5) returns 5.0
(float 3.5) returns 3.5 [No effect, but no error]
(float "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(float "3.5") returns "Error: Bad Argument Type" ["3.5" is a string, not a number]
(float "abc") returns "Error: Bad Argument Type" ["abc" is a string, not a number]
Example Program 1:
(defun C:myProg()
(setq intAge(getint "\n Enter your Age: "))
(setq intDays(* intAge 365))
(princ (strcat "\n You are " (itoa intDays) " Days old!"))
(princ)
Execution:
Command: Enter your Age: 39<enter>
Command: You are 14235 Days old!
List Functions :
car cdr cadr caddr caar cddr foreach list cons nth
Example Programs
You are about to unravel the mystery behind the car of a cdr. Better sit down.
- 14 -
car - This function returns the first item of a list. The item can be a list as shown in example 3 below.
Syntax : (car list)
list - Any valid list.
(car (1 2 3)) returns 1
(car ("ab" "cde" "Jeff")) returns "ab"
(car ((1 2 3) (4 5 6))) returns (1 2 3)
(car 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(car "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(car (1 (2 3))) returns 1
(car ((1 2) 3)) returns (1 2)
This function is mainly used to get the x coordinate of a point. [ (car (x y z)) returns x ]
cdr - This function returns a list that includes everything but the first item in a list. The item can be a list as shown in
example 3 below.
Syntax : (cdr list)
(cdr (1 2 3)) returns ( 2 3)
(cdr ("ab" "cde" "Jeff")) returns ("cde" "Jeff")
(cdr ((1 2 3) (4 5 6))) returns (4 5 6) since (4 5 6) is the second item in the list.
(cdr 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(cdr "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(cdr (1 (2 3))) returns (2 3)
(cdr ((1 2) 3)) returns 3
Mystery HINT: (car (cdr ( 1 (2 3) ) ) ) returns 2 [So, that's what a car of a cdr is]
if the cdr of (1 (2 3)) returns (2 3) and the car of (2 3) returns 2 then the mystery is solved.
The car of a cdr is the first item in the second item in the list.
- 15 -
cadr - This function returns the second item in a list. The item can be a list as shown in example 3 below.
Syntax : (cadr list)
(cadr (1 2 3)) returns 2
(cadr ("ab" "cde" "Jeff")) returns "cde"
(cadr ((1 2 3) (4 5 6) (7 8 9))) returns (4 5 6)
(cadr 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(cadr "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(cadr (1 (2 3))) returns (2 3)
(cadr ((1 2) 3)) returns 3
(cadr (1)) returns nil [There isn't a second item]
This function is mainly used to get the y coordinate of a point. [ (cadr (x y z)) returns y ]
caddr - This function returns the third item in a list. The item can be a list as shown in example 3 below.
Syntax : (caddr list)
(caddr (1 2 3)) returns 3
(caddr ("ab" "cde" "Jeff")) returns "Jeff"
(caddr ((1 2 3) (4 5 6) (7 8 9))) returns (7 8 9)
(caddr 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(caddr "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(caddr (1 (2 3))) returns nil [There isn't a third item]
(caddr ((1 2) 3 (5 6) 7)) returns (5 6)
(caddr (1)) returns nil [There isn't a third item]
This function is mainly used to get the z coordinate of a point. [ (caddr (x y z)) returns z ]
caar - This function returns the first item of the first item in a list. The item can be a list as shown in example 3
below.
- 16 -
Syntax : (caar list)
(caar (1 2 3)) returns "Error: Bad Argument Type" [The first item in the list is not a list]
(caar ((1 2 3)(4 5 6)) returns 1
(caar (("ab" "cde") ("Jeff")) returns "ab"
(caar (("Jeff" 1 2 3)("x" "y" "z")(4 5 6))) returns "Jeff"
(caar 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(caar "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(caar (1 (2 3))) returns "Error: Bad Argument Type" [The first item in the list is not a list]
(caar ((1 2) 3)) returns 1
cddr - This function returns a list that includes everything after the second item in a list.
Syntax : (cddr list)
(cddr (1 2 3)) returns (3)
(cddr ("ab" "cde" "Jeff" "Sanders")) returns ("Jeff" "Sanders")
(cddr ((1 2 3) (4 5 6) (7 8 9)(10 11 12))) returns ((7 8 9)(10 11 12))
(cddr 1) returns "Error: Bad Argument Type" [1 is an integer, not a list]
(cddr "Jeff") returns "Error: Bad Argument Type" ["Jeff" is a string, not a list]
(cddr (1 (2 3))) returns nil [There isn't a third item]
(cddr ((1 2) 3 (5 6) 7)) returns ((5 6) 7)
(cddr (1)) returns nil [There isn't a third item]
foreach - This function steps through each item in the list and returns the last value.
Syntax : (foreach varName list yourFunctions)
varName - Any valid variable name that you make up.
yourFunctions - Any valid autolisp functions.
- 17 -
(foreach a (list 1 2 3)(princ a)) prints 123 to the screen and returns 3 [same as
(princ 1) (princ 2) (princ 3) except that it only returns the last value.]
(foreach a (list 1 2 3)(princ (+ a 5))) prints 678 to the screen and returns 8
[same as (princ (+ 1 5)) (princ (+ 2 5)) (princ (+ 3 5)) except that it only returns the last value.]
list - This function creates a list.
Syntax : (list Item)
Syntax : (list firstItem secondItem)
Syntax : (list firstItem secondItem thirdItem...)
Item - Any valid item including a list.
(list) returns nil [an Empty list]
(list 1 2 3) returns (1 2 3)
(list "ab" "cde" "Jeff" "Sanders") returns ("ab" "cde" "Jeff" "Sanders")
(list (list 1 2 3) (list 4 5 6)) returns ((1 2 3) (4 5 6))
(list 1) returns (1)
(list "Jeff") returns ("Jeff")
(list 1 (list 2 3)) returns (1 (2 3))
(list (list 1 2) 3 (list 5 6) 7) returns ( (1 2) 3 (5 6) 7)
cons - This function takes an item and a list, and returns the addition of that item to the beginning of the list. The first item
can be an atom or a list.
Syntax : (cons Item list) ;thanks tim!
Item - Any valid item including a list.
(cons) returns "Error: Too Few Arguments" [cons requires an item and a list]
(cons 1 2 3) returns "Error: Too Many Arguments" [cons requires an item and a list]
(cons "ab" (list "cde" "Jeff" "Sanders")) returns ("ab" "cde" "Jeff" "Sanders")
(cons (list 1 2 3) (list 4 5 6)) returns ((1 2 3) 4 5 6)
- 18 -
(cons 1) returns "Error: Too Few Arguments" [cons requires an item and a list]
(cons "Jeff") returns "Error: Too Few Arguments" [cons requires an item and a list]
(cons 1 (list 2 3)) returns (1 2 3) [notice the difference here from the list function above]
(cons "Jeff" (list 1 2 3 5 6 7)) returns ( "Jeff" 1 2 3 5 6 7 )
nth - This function returns the Nth item in a list. The first item in a list is item zero.
Syntax : (nth integer list)
integer - Any valid integer.
(nth) returns "Error: Too Few Arguments" [cons requires an item and a list]
(nth 2 1 2 3) returns "Error: Bad Argument Type" [nth requires an integer and a list]
(nth 2 (list "cde" "Jeff" "Sanders")) returns "Sanders"
(nth 0 (list 1 2 3)) returns 1
(nth 1 (list "a" (list "b" "c") "d")) returns ("b" "c")
(nth 4 (list 1 2 3 5 6 7)) returns 6
Example Program 1:
(defun C:myProg() [define program]
(setq pt1(getpoint "\n First Corner: ")) [get first point]
(setq pt2(getcorner pt1 "\n Last Corner: ")) [get other point on a square]
(setq x1(car pt1)) [get x coordinate of pt1]
(setq x2(car pt2)) [get x coordinate of pt2]
(setq y1(cadr pt1)) [get y coordinate of pt2]
- 19 -
(setq y2(cadr pt2)) [get y coordinate of pt2]
(setq hor1(- x2 x1)) [get horizontal distance]
(setq ver1(- y2 y1)) [get vertical distance]
(princ "\n Horizontal Distance = ")(princ hor1) [print to screen]
(princ "\n Vertical Distance = ")(princ ver1) [print to screen]
(princ) [supress echo..clean exit]
) [close program]
Execution:
Command: First Corner: <pick a point>
Command: Last Corner: <pick a point>
Command: Horizontal Distance = 23.5
Command: Vertical Distance = 11.5
Example Program 2:
(defun C:AddText() [define program]
(setq myList(list "e" "b" "c" "m" "at")) [make a list of 6 letters]
(foreach myVar myList [start the foreach loop]
(princ (strcat myVar (nth 4 myList))) [define a valid function]
) [close the foreach statement]
(princ) [supress echo..clean exit]
) [close program]
Execution:
Command: (load "AddText")<enter>
- 20 -
Command: AddText<enter>
Command: eat
Command: bat
Command: cat
Command: mat
Command: atat
End of List Functions
Entity DXF Group Codes
All entities inside an AutoCAD drawing has DXF Group codes. The group codes define the properties of each entity. Each
code inside the group is acutally an associtated list. The group codes for a line may look something like this:
((-1 . <Entity name: 3b40868>) (0 . "LINE") (5 . "BD") (100 . "AcDbEntity")

(67 . 0) (8 . "DIM") (100 . "AcDbLine") (10 200.25 316.75 0.0)
(11 242.25 316.75 0.0) (210 0.0 0.0 1.0))
Where:
Group code -1 is the name of the entity.
Group code 0 is the type of entity.
Group code 8 is the layer name.
Group code 10 is the start point of the line.
Group code 11 is the end point of the line.
The group codes for a circle may look something like this:
((-1 . <Entity name: 3b40cf0>) (0 . "CIRCLE") (5 . "146") (100 . "AcDbEntity") (67 .

0) (8 . "HOL") (100 . "AcDbCircle") (10 163.135 367.479 0.0) (40 .
2.56277) (210 0.0 0.0 1.0))
Where:
Group code -1 is the name of the entity.
- 21 -
Group code 0 is the type of entity.
Group code 8 is the layer name.
Group code 10 is the center of the circle.
Group code 40 is the radius of the circle.
How do you list the codes for an entity? Type this at the command line, press enter, and select an entity.
(entget(car(entsel)))
Entsel selects the entity, car gets the entity name from entsel, and entget returns the Group Codes of the entity.
What are the numbers in the group code for? They aide in extracting data from the group codes. Take for instance this
code:
(setq entList(entget (car (entsel))))
If I selected a circle, this code would set entList to something like this:
((-1 . <Entity name: 3b40cf0>) (0 . "CIRCLE") (5 . "146") (100 . "AcDbEntity") (67 .

0) (8 . "HOL") (100 . "AcDbCircle") (10 163.135 367.479 0.0) (40 .
2.56277) (210 0.0 0.0 1.0))
If I wanted to extract data from this group code list I would simply type:
(assoc 40 entList) ;would return 2.56277
(assoc 0 entList) ;would return "CIRCLE"
(assoc 10 entList) ;would return (163.135 367.479 0.0)
(assoc 8 entList) ;would return "HOL"
An associated list can make extraction a very easy thing to accomplish.
Conversion Functions:
fix float itoa atoi atof rtos angtos
fix - This function returns an integer. (NOTE: This function does not round numbers off!)
Syntax : (fix number)
- 22 -
(fix 345) returns 345
(fix 345.9) returns 345
(fix -345) returns -345
(fix -345.9) returns -345
(fix "345JEFF") returns "Error: Bad Argument Type" ["345JEFF" is a string, not a number]
float - This function returns a real number.
Syntax : (float number)
(float 345.9) returns 345.9
(float -345) returns -345.0
(float -345.9) returns -345.9
(float "345JEFF") returns "Error: Bad Argument Type" ["345JEFF" is a string, not a number]
itoa - This function changes an integer to a string.
Syntax : (itoa integer)
integer - any valid integer.
(itoa 345.9) returns "Error: Bad Argument Type" [345.9 is a real number, not an integer]
(itoa -345) returns "-345"
(itoa -345.9) returns "Error: Bad Argument Type" [-345.9 is a real number, not an integer]
(itoa "345JEFF") returns "Error: Bad Argument Type" ["345JEFF" is a string, not an integer]
atoi - This function changes a string into an integer.
- 23 -
Syntax : (atoi string)
string - any valid string.
(atoi "345") returns 345
(atoi "345.9") returns 345
(atoi 345) returns "Error: Bad Argument Type" [345 is a number, not a string]
(atoi 345.9) returns "Error: Bad Argument Type" [345.9 is a number, not a string]
(atoi "-345") returns -345
(atoi "-345.9") returns -345
(atoi "345JEFF49") returns 345
(atoi "JEFF49") returns 0
Note: This function starts at the beginning of the string and continues until it finds a character that cannot be an integer.
atof - This function changes a string into a real number.
Syntax : (atof string)
string - any valid string.
(atof "345") returns 345.0
(atof "345.9") returns 345.9
(atof 345) returns "Error: Bad Argument Type" [345 is a number, not a string]
(atof 345.9) returns "Error: Bad Argument Type" [345.9 is a number, not a string]
(atof "-345") returns -345.0
(atof "-345.9") returns -345.9
(atof "345JEFF49") returns 345.0
(atof "JEFF49") returns 0.0
Note: This function starts at the beginning of the string and continues until it finds a character that cannot be a number.
rtos - This function converts numbers to a formatted string representing a distance.
- 24 -
Syntax : (rtos number mode precision)
number - Any valid number. [Real or Integer]
mode - This directly corresponds to LUnits system variable.
precision - This directly corresponds to the LUPrec system variable.
mode = 1 = Scientific
with precision = 1 (rtos 456.5 1 1) returns "4.6E+02"
ect.....
mode = 2 = Engineering
with precision = 1 (rtos 456.5 2 1) returns "456.5"
ect.....
mode = 3 = Decimal
with precision = 1 (rtos 456.5 3 1) returns "38'-0.5""
- 25 -
with precision = 7 (rtos 456.5 3 7) returns "38'-0.5000000"
ect.....
mode = 4 = Architectural
with precision = 1 (rtos 37.7071 4 1) returns "3'-1 1/2""
ect.....
mode = 5 = Inch Fractional
with precision = 1 (rtos 37.7071 5 1) returns "371/2""
with precision = 2 (rtos 37.7071 5 2) returns "37 3/4""
ect.....
angtos - This function converts a number to a formatted string representing an angle.
Syntax : (angtos number mode precision)
- 26 -
number - Any valid number representing radians. [3.14159 radians = pi =180 degrees]
mode - This directly corresponds to AUnits system variable.
precision - This directly corresponds to the AUPrec system variable.
mode = 0 = Decimal Degrees
with precision = 1 (angtos 0.627102 0 1) returns "35.9"
ect.....
mode = 1 = Degrees Minutes Seconds
with precision = 1 (angtos 0.627102 1 1) returns " 35d56' "
with precision = 3 (angtos 0.627102 1 3) returns " 35d55'49" "
with precision = 5 (angtos 0.627102 1 4) returns " 35d55'49.1" "
ect.....
mode = 2 = Grads
with precision = 1 (angtos 0.627102 2 1) returns "39.9g"
ect.....
mode = 3 = Radians
with precision = 1 (angtos 0.627102 3 1) returns "0.6r"
- 27 -
ect.....
mode = 4 = Surveyor
with precision = 1 (angtos 0.627102 0 1) returns "N 54d4' E"
with precision = 2 (angtos 0.627102 0 2) returns "N 54d4' E"
with precision = 3 (angtos 0.627102 0 3) returns "N 54d4'11" E"
with precision = 4 (angtos 0.627102 0 4) returns "N 54d4'11" E"
with precision = 5 (angtos 0.627102 0 5) returns "N 54d4'10.9" E"
ect.....
Math Functions
+ - / * 1+ 1- cos atan sin sqrt expt Example Program
+ - Addition.
Syntax : (+ number number)
(+ 3 4) returns 7
(+ 3.5 4.2) returns 7.7
(+ 3 4 5) returns 12
(+ 1.2 1.2 1.2) returns 3.6
(+ "3" "4") returns "Error: Bad Argument Type" ["3" and "4" are strings, not numbers]
- 28 -
- - Subtraction.
Syntax : (- number number)
(- 4 3) returns 1
(- 4.5 4.2) returns 0.3
(- 9 5 2) returns 2
(- 40.5 10.0 5.2) returns 25.3
(- "3" "4") returns "Error: Bad Argument Type" ["3" and "4" are strings, not numbers]
/ - Division.
Syntax : (/ number number)
(/ 9 3) returns 3
(/ 5 2) returns 2 [if both numbers are integers then it returns an integer]
(/ 5 2.0) returns 2.5 [if either number is a real number then it returns a real number]
(/ 5.0 2) returns 2.5 [if either number is a real number then it returns a real number]
(/ 12 2 3) returns 2 [12/2 = 6 then 6/3 = 2 ]
(/ "3" "4") returns "Error: Bad Argument Type" ["3" and "4" are strings, not numbers]
* - Multiplication.
Syntax : (* number number)
- 29 -
(* 9 3) returns 12
(* 5 2) returns 10 [if both numbers are integers then it returns an integer]
(* 5 2.0) returns 10.0 [if either number is a real number then it returns a real number]
(* 5.0 2) returns 10.0 [if either number is a real number then it returns a real number]
(* 2 3 4) returns 24 [2*3 = 6 then 6*4 = 24 ]
(* "3" "4") returns "Error: Bad Argument Type" ["3" and "4" are strings, not numbers]
1+ - Returns value increased by one.
Syntax : (1+ number)
(1+ 3) returns 4
(1+ 5) returns 6 [if the number is an integer then it returns an integer]
(1+ 5.0) returns 6.0 [if number is a real number then it returns a real number]
(1+ "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(1+ 3 4) returns "Error: Too Many Arguments" [Only accepts one number as argument]
1- - Returns value decreased by one.
Syntax : (1- number)
(1- 3) returns 2
(1- 5) returns 4 [if the number is an integer then it returns an integer]
(1- 5.0) returns 4.0 [if number is a real number then it returns a real number]
(1- "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(1- 3 4) returns "Error: Too Many Arguments" [Only accepts one number as argument]
- 30 -
cos - Returns the cosine of an angle expressed in radians.
(Note: Radians are AutoCads angular units. A circle = 2*pi or 180 degrees = pi )
Syntax : (cos number)
number - any valid number.[integer or real number] that represents an angle expressed in radians.
Returns a real number.
(cos pi) returns -1.0
(cos (+ pi pi)) returns 1.0
(cos 5.0) returns 0.283662
(cos "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(cos 3 4) returns "Error: Too Many Arguments" [Only accepts one number as argument]
atan - Returns the arctangent of a number in radians.
Syntax : (atan number1 ....optional number2)
number1 - any valid number.[integer or real number].
number2 - any valid number.[integer or real number]. This is optional and is usually omitted.
Returns a real number representing radians.
(atan 1) returns 0.785398
(atan -1) returns -0.785398
(atan 5.0) returns 1.3734
(atan "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(atan 3 4) returns 0.643501 [Returns the arctangent of 3 divided by 4]
(Note: The range of angles returned is -pi/2 to +pi/2 radians. )
sin - Returns the sine of an angle expressed in radians.
- 31 -
Syntax : (sin number)
number - any valid number.[integer or real number] that represents an angle expressed in radians.
(sin 1.0) returns 0.841471
(sin 0) returns 0.0
(sin 5.0) returns -0.958924
(sin "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(sin 3 4) returns "Error: Too Many Arguments" [Only accepts one number as an argument]
sqrt - Returns the square root of a number.
Syntax : (sqrt number)
number - any valid number.[integer or real number].
(sqrt 4) returns 2.0
(sqrt 0) returns 0.0
(sqrt 5.0) returns 2.23607
(sqrt "3") returns "Error: Bad Argument Type" ["3" is a string, not a number]
(sqrt 3 4) returns "Error: Too Many Arguments" [Only accepts one number as argument]
expt - Returns a number raised to a power.
Syntax : (expt number power)
number - any valid number.[integer or real number].
power - any valid number.[integer or real number].
Returns a real number unless both number and power are integers, then it returns an integer..
(expt 2 2) returns 4
- 32 -
(expt 2 2.0) returns 4.0
(expt 5 2) returns 25
(expt "3" 2) returns "Error: Bad Argument Type" ["3" is a string, not a number]
Example Program 1:
(defun C:myProg()
(setq intAge(getint "\n Enter your Age: "))
(setq intDays(* intAge 365))
(setq intWeeks(/ intDays 7))
(princ (strcat "\n You are " (itoa intDays) " Days old!"))
(princ (strcat "\n You are " (itoa intWeeks) " Weeks old!"))
(princ)
Execution:
Command: Enter your Age: 39<enter>
Command: You are 14235 Days old!
Command: You are 2033 Weeks old!
Example Program 2:
(defun C:Triangle()
(setq pt1(getpoint "\n Pick First Point: "))
(setq pt2(getpoint "\n Pick Last Point: "))
(setq x1(car pt1)) ;x-coord of point one
(setq x2(car pt2)) ;x-coord of point two
- 33 -
(setq y1(cadr pt1)) ;y-coord of point one
(setq y2(cadr pt2)) ;y-coord of point two
(setq xdis(- x2 x1)) ;distance in x direction between points
(setq ydis(- y2 y1)) ;distance in y direction between points
(setq slpdis(sqrt(+ (expt xdis 2.0)(expt ydis 2.0)))) ;A sq + B sq = C sq
(princ (strcat "\n Distance = " (rtos slpdis 4 4)))
(princ)
Execution:
Command: (load "Triangle")<enter>
Command: Triangle<enter>
Command: Pick First Point:<pick>
Command: Pick Last Point:<pick>
Command: Distance = 3'-4 1/2"
Command:
Selecting Entities
Functions - entsel ssget Example Programs
entsel - This function prompts for the user to pick one entity.
Syntax : (entsel)
Returns the entity's name and the point selected in a list.
Example: (<Entity name: 3b40a08> (230.666 285.862 0.0))
(car(entsel)) returns the entity name if entsel does not return nil..
(cadr(entsel)) returns the point selected if entsel does not return nil..
- 34 -
Note: Selecting an area in the drawing where there are no entities would return nil. You will get an error
if you try to get the car or cadr of nil as shown above. The best thing to do is to save the return value of the entsel
function, then check to see if it is a valid selection.
Example:
(setq myEnt(entsel)) ; save the return value of the entsel function
(if myEnt ; if the value of myEnt is not nil then do some stuff
(progn ; use the progn statement here for multiple statements
;do some stuff ; put your code here
) ; close the progn statement here
(alert "Nothing Selected.") ; alert the user
) ; close the if statement
ssget - This function prompts the user to select entities.
Syntax : (ssget) ;prompts the user for a selection set.
Syntax : (ssget mode) ;prompts the user for a selection set and sets mode to "W", "C", "L", and "P",
corresponding to the Window, Crossing, Last, and Previous selection methods. Another
optional mode value is "X", which selects the entire database. There are other modes, but this
list contains the modes that will be used most often.
Syntax : (ssget "W" ) ;prompts the user for a selection set using the Window mode.
Syntax : (ssget "C" ) ;prompts the user for a selection set using the Crossing mode.
Syntax : (ssget "L" ) ;Selects the last entity selected.
Syntax : (ssget "P" ) ;Selects the previously selected entities.
Syntax : (ssget "X" ) ;Selects all entities in the drawing.
Syntax : (ssget filter_List) or (ssget mode filter_List)
filter_List - an association list containing valid filters for entities corresponding to the Entity DXF Group
Codes. What did I just say? Entity DXF Group Codes? What the heck is that?
Click here to find out.
You can filter out enitites that do no match your criteria using the filter_List. If you only
wanted entities that were on layer "STR" then you could add a filter list that looks like this:
(setq myFilter(list (cons 8 "STR"))) ;returns ((8 . "STR"))
- 35 -
(ssget "X" myFilter) ;returns a selection set containing only entities on layer "STR"
or
(setq myFilter(list (cons 0 "LINE")(cons 8 "STR")))
;returns ((0 . "LINE")(8 . "STR"))
(ssget "X" myFilter)
;returns a selection set containing only line entities on layer "STR"
Returns a selection set of entity names.
End of Selecting Entities
Example Program 1:
(defun C:myProg()
(if (setq myEnt(entsel)) ;start the if statement
(progn ;going to have multiple statements
(setq pt1(getpoint "\n Base Point: ")) ;store base point
(setq pt2(getpoint "\n Displacement Point: ")) ;store displacement pt
(command "move" (car myEnt) "" pt1 pt2) ;move entity
) ;close the progn
(alert "Please select an entity!") ;else alert the user of an error
) ;close the if statement
Execution:
Command: Select Object: <pick>
Command: Base Point: <pick>
- 36 -
Command: Displacement Point: <pick>
Command:
Example Program 2:
(defun C:myProg2()
(if (setq mySet(ssget "X" (list (cons 8 "STR")(cons 0 "CIRCLE")))) ;get set
(progn ;going to have multiple statements
(setq pt1(getpoint "\n Base Point: ")) ;store base point
(setq pt2(getpoint "\n Displacement Point: ")) ;store displacement pt
(command "move" mySet "" pt1 pt2) ;move all entities
) ;close the progn
(alert "No entites Match Criteria!") ;else alert the user of an error
Execution:
Command: (load "myProg2")<enter>
Command: myProg2<enter>
Command: Base Point: <pick>
Command: Displacement Point: <pick>
Command:
election Set Functions

Functions - ssadd ssdel sslength ssname Example Programs
ssadd - This function does one of three things depending on how many arguments you send with it.
If you use the ssadd function with no arguments it will return a new selection set with no members.
- 37 -
Example : (setq myNewSet(ssadd))
If you use ssadd with a name of an entity it will return a new selection set with only that one member.
Example : (setq myNewSet(ssadd entityName))
If you use ssadd with a name of an entity and name of an selection set, it will add that entity to the set.
Example : (setq myOldSet(ssadd entityName selectionSetName))
And return the selection set with the entity added to the set.
Syntax : (ssadd) (ssadd entityName) (ssadd entityName SelectionSetName)
Where entityName is a valid entity name returned by ssname or entsel.
Where selectionSetName is a valid name of a selection set returned by setq.
Returns the selection set with the new entity added to it.
Example: (<Selection set: 1>
Example: Let's build a function that allows me to add items to a selection set until I stop.
(defun C:BldSet() ;defin a program name
(setq mySet(ssadd)) ;build an empty selection set
(while(/= (setq enS(entsel)) nil) ;loop until I pick nothing or press enter.
(setq en(car enS)) ;get the entity name of the selected item
(setq mySet(ssadd en mySet)) ;add the entity to the selection set
Now at the Command prompt type:
Command: move<enter>
Command: !mySet<enter> ;don't forget the exclamation point in front of the variable name.
Did everything get selected to be moved? Cool. Move individual items around and try it again. Did everything get
selected again? Cool. Why? Because AutoLisp finds them by their entity name, not their location.
ssdel - This function does the opposite of ssadd. SSDEL removes an entity from a selection set.
- 38 -
Syntax : (ssdel entityName selectionSetName)
Where entityName is a valid entity name returned by ssname or entsel.
Returns a new selection set without the entity.
Assuming en1 is a valid entity and en2 is not.
Assuming ss1 is a valid selection set and ss2 is not.
Assuming en3 is a valid entity name but is not part of any selection set.
(ssdel en1 ss1) ;returns selection set without entity en.
(ssdel en1 ss2) ;returns ERROR - Bad Argument Type
(ssdel en3 ss1) ;returns nil
Note: If you filter correctly using the ssget "X" function, you shouldn't need ssdel.
sslength - This function returns the number of entities inside a selection set.
Syntax : (sslength selectionSetName)
Returns a real number if the number is greater than 32,767, otherwise it returns an integer.
The number, real or integer, represents the quantity of items inside the selection set.
Assuming ss1 is a valid selection set containing 15 entities.
Assuming ss2 is a valid selection set containing 1 entity.
Assuming ss3 is a valid selection set containing no entities.
Assuming ss4 is a valid selection set containing 40,000 entities.
Assuming ss5 is not a valid selection set.
(sslength ss1) ;returns 15 as an integer
- 39 -
(sslength ss4) ;returns 40000.0 as a real number
(sslength ss5) ;returns ERROR - Bad Argument Type
ssname - This function returns an entity name contained inside a selection set.
Syntax : (ssname selectionSetName nthItem)
Where nthItem is an integer representing an index into the set.
Note: nthItem needs to be a real if the set contains more than 32,767 items.
Returns an entity's name on success and nil on error.
Assuming ss1 is a valid selection set containing 15 entities.
Assuming ss2 is a valid selection set containing 40,000 entities.
Assuming ss3 is not a valid selection set.
(ssname ss1 0) ;returns the first entity in the selection set.
(ssname ss1 3) ;returns the fourth entity.
(ssname ss1 24) ;returns nil
(ssname ss1 -3) ;returns nil
(ssname ss2 34555) ;returns ERROR - Bad Argument Type (needs real)
(ssname ss2 34555.0) ;returns the 34555th entity
End of Selection Set Functions
Example Program 1:
I will write a program that prints the layer name of every entity in a selection set.
(defun C:pLay() ;define a program name
(if (setq eset(ssget) ;use the ssget function to select entities
- 40 -
(progn ;use progn since there will be more than 1 statement
(setq cntr 0) ;set the cntr to the first item in the set
(while (< cntr (sslength eset)) ;while cntr is less than the length of the set
;note: the length is one more than the index of items since the first item is zero. In other words, to get to the ;
first item in a selection set consisting of one item you would use (ssname eset 0) not (ssname eset 1).
(setq en(ssname eset cntr)) ;get the entity name of the item indexed with cntr
(setq enlist(entget en)) ;get the dxf group codes of the enitity
(setq layName(cdr(assoc 8 enlist))) ;get the layer name
(princ "\n ") ;print "\n " will cause a new line to be printed
(princ layName) ;print the layer name to the command line
(setq cntr(+ cntr 1)) ;increment the counter
) ;close the while statement
) ;close the progn on the if statement
(princ "\n Error - No entities selected.") ;print a message on the else statement
; note: the if statement can be a " if then " statement or a " if then else" statement
Note: I personally do not find any of these functions useful except for the ssname and sslength functions.
If you use your ssget "X" filters well enough there is no reason for the ssadd or ssdel statements.
There are other selection set functions that are even less useful such as ssmemb, sssetfirst, & ssgetfirst.
When you loop through your selection set you can check an entities DXF group codes and decide whether the entity is
one to either skip or work on. So, you can avoid all of these useless functions. Don't get me wrong. I'm not saying they
are completely useless and you shouldn't use them. I'm saying why bother.
Entity Functions
entget entlast entnext entdel entmod entupd Example Program
- 41 -
entget - This function returns the DXF Group Codes of the entity.
Syntax : (entget ename)
ename - a valid entity name returned by entsel, ssname, entlast, or the entnext function.
Returns an Entity's DXF Group Codes as an association list.
(setq en(car(entsel))) returns entity name as eg. <Entity name: 3b40a60>
(entget en) returns :
((-1 . <Entity name: 3b40a60>) (0 . "LINE") (5 . "FC") (100 . "AcDbEntity") (67 . 0) (8 . "DIM")
(100 . "AcDbLine") (10 252.578 68.25 0.0) (11 188.379 31.5 0.0) (210 0.0 0.0 1.0))
entlast - This function returns the name of the last non-deleted entity in the drawing.
Syntax : (entlast)
This function is mainly used to get the last entity added to the drawing.
Returns an entity name.
(entlast) returns <Entity name: 3b40a60>
entnext - Let's look at AutoDesk's explanation: If entnext is called with no arguments, it returns the entity name
of the first nondeleted entity in the database. If entnext is called with an entity name argument ename, it
returns the entity name of the first nondeleted entity following ename in the database. If there is no next
entity in the database, it returns nil. The entnext function returns both main entities and subentities.
The entities selected by ssget are main entities, not attributes of blocks or vertices of polylines. You can
access the internal structure of these complex entities by walking through the subentities with entnext.
Once you obtain a subentity's name, you can operate on it like any other entity. If you obtain the name
of a subentity with entnext, you can find the parent entity by walking forward with entnext until a seqend
entity is found, then extracting the -2 group from that entity, which is the main entity's name.
Syntax : (entnext) or (entnext ename)
(entnext) returns the name of the first entity in the drawing.
(entnext ename) returns the name of the next entity following ename.
- 42 -
entdel - This function deletes an entity from the drawing if it exist. If it does not exist and has been previously
deleted, it will undelete the entity.
Syntax : (entdel ename)
(setq en(car(entsel))) returns the name of selected entity.
(entdel en) deletes the entity and returns the name of the deleted entity.
(entdel en) undeletes the entity and returns the name of the undeleted entity.
entmod - Modifies an entity in the AutoCAD database.
Syntax : (entmod elist)
elist - a list that is returned from an entget statement. (DXF Group Codes of an entity)
Returns an elist if successful otherwise it returns nil.
(setq en(car(entsel))) returns the name of selected entity.
(setq elist(entget en)) returns the DXF Group Codes of the entity.
(setq elist(subst (cons 8 "DIM")(assoc 8 elist) elist))
The line above Replaces existing layer name in the elist with new layer name "DIM"
(entmod elist) updates the AutoCAD database and replaces the old layer name with the new one.
entupd - Updates the screen image of an entity.
Syntax : (entupd ename)
(setq en(car (entsel))) returns an entity name.
(entupd ename) refreshes the entity on the graphics screen.
Note: If you modify the DXF Group Codes of an entity, such as changing the layer (8 . "LAyerName"), you
will not notice the change until you regenerate the entire drawing or use entupd to regenerate the entity.
- 43 -
End of Entity Functions
Example Program 1:
Let's change an entity's layer to a layer named "DIM".
(defun C:CLay()
(if(setq ent(entsel))
(progn
(setq en(car ent))
(setq enlist(entget en))
(setq enlist (subst (cons 8 "Dim")(assoc 8 enlist)enlist))
(entmod enlist)
(entupd en)
(alert "Error - Select an entity please.")
(princ)
Execution:
Command: (load "CLay")<enter>
Command: CLay<enter>
Command: Select Object:<pick>
Command:
Read/Write & File Functions

Functions - open/close read-line write-line Example Programs
- 44 -
open/close - Open a file and close a file. That simple.
Syntax : (open "filename" mode) (close fileVarName)
Where filename is any valid file or resource name.
Where mode is either "r" , "w" , or "a".
"r" - Read mode. Reads a file with either read-char or read-line.
"w" - Write mode. Writes to a file with either write-char, write-line, princ, or print.
"a" - Append mode. Appends to an existing file using write-char, write-line, princ, or print.
Note: If the existing file is not found in append mode, autolisp will create a new empty file.
Open Returns a file descriptor.
Note: You must use (setq varNam(open "file" mode)) to enable closing of the file.
Note: Writing the file does not occur until you use the close statement.
.
Example:
(if (setq f(open "c:/acad/myfile.txt" "r"))
(progn
(while (setq txtLine(read-line f))
(princ txtLine)
(close f)
(princ "\n Error - File was not opened.")
read-line - This function reads a line of text from an open file.
Syntax : (read-line fileVar)
Where fileVar is a valid variable name that represents an open file descriptor.
Returns a text string.
- 45 -
Assuming (setq f(open "text.txt" "r")) returned sucessfully.
Assuming (setq g(open "text8.txt" "r")) failed.
(read-line f) ;returns string from file
(read-line g) ;returns Error - Bad Argument Type
write-line - This function writes a line of text to an open file.
Syntax : (write-line fileVar)
Where fileVar is a valid variable name that represents an open file descriptor.
Returns a text string.
Assuming (setq f(open "text.txt" "r")) returned successfully.
Assuming (setq g(open "text8.txt" "r")) failed.
(write-line "Hello World" f) ;writes text to file and returns string "Hello World"
(write-line "Hello World" g) ;returns Error - Bad Argument Type
End of Read/Write and File Functions
Final note:
I've stated over and over that the OPEN statement opens a file. This can also be any resource available to you. Instead of
opening "C:\ACAD\MyTextFile.txt" you can just as easily open "LPT1" or "\\myserver\myprinter" and write the file to a
printer exactly like you write to a file. Cool! Printing from AutoLisp!
One thing to keep in mind. The file does not get written to disk or sent to the printer until after the CLOSE statement. [ This
will help you when debugging.] If you cannot get a printer to print, write the data into a text file instead of the printer. Then
open the file with notepad and see if it is what you expect. If the data looks good in notepad then you've probably got the
printer name wrong, a printer problem, or a network access problem.
Example Program 1:
Let's write a program that prints a text file on the command line.
(defun C:pTxt() ;define a program name
(setq fname(getstring "\n Enter a valid file name: ")) ;get file name cheaply
- 46 -
(if(setq f(open fname "r")) ;open the file in read mode
(while (setq txtLine(read-line f)) ;while lines of text exist in file
(princ txtLine) ;print the text string to the command line
) ;close the while statement
(princ "\n Error - Could not find file") ;print a message on the else statement
; note: the if statement can be a " if then " statement or a " if then else" statement
Entity DXF Group Code Table
Entity Types: (Group Code 0)
LN = Line CI = Circle AR = Arc TR = Trace SD = Solid TX = Text 3DF = 3DFace AD =

AttDef
PT = Point PL = PolyLine VT = Vertex DM = Dimension AT = Attribute IN = Insert SQ = Seqend
|--------------------- Entity Type (Group Code 0) -----------------------|
CODE DESCRIPTION LN PT CI AR TR SD TX SH IN AD AT PL VT DM 3DF SQ
Entity Name
-1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
(Primary)
Entity Name
-2 -2
(Secondary)
Primary Text
1 1 1 1 1
Value
Name: Shape,
2 2 2 2 2 2
Block, Tag
3 Prompt String 3
- 47 -
Handle
5 (Hexadecimal 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
String)
6 LineType Name 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
7 Text Style Name 7 7 7
8 Layer Name 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
X of Start or Insert
10 10 10 10 10 10 10 10
Point
X of Center Point 10 10
X of Corner Point 10 10 10
10
X of Definition
10
Point
X of Elev. Point
10
(2D Poly)
X of End or
11
Insertion Point
11 X of Alignment
11 11 11
Point
X of Middle Point
11
of Dimension
12 X of Insertion
12
Point
13 X of Definition
13
Point
- 48 -
X of Definition
14 14
Point
X of Definition
15 15
Point
X of Definition
16 16
Point
Y of Start or
20 20 20 20 20 20 20 20
Insertion Point
Y of Center Point 20 20
Y of Corner Point 20 20 20
20
Y of Definition
20
Point
Y of Elev. Point
20
(2D Poly)
Y of End or Insert
21
Point
21 Y of Alignment
21 21 21
Point
Y of Middle Point
21
of Dimension
- 49 -
22
Y of Insert Point 22
23 Y of Definition
23
Point
Y of Definition
24 24
Point
Y of Definition
25 25
Point
Y of Definition
26 26
Point
Z of Start or Insert
30 30 30 30 30 30 30 30
Point
Z of Center Point 30 30
Z of Corner Point 30 30 30
30
Z of Definition
30
Point
Z of Elevation
30
Point (2D Poly)
Z of End Point 31
31 Z of Alignment
31 31 31
Point
Z of Middle Point
31
of Dimension
32 Z of Corner Point 32 32 32
- 50 -
Z of Insert Point 32
33 Z of Definition
33
Point
Z of Definition
34 34
Point
Z of Definition
35 35
Point
Z of Definition
36 36
Point
38 Entity Elevation 38 38 38 38 38 38 38 38 38 38 38 38 38 38
39 Entity Thickness 39 39 39 39 39 39 39 39 39 39 39 39 39 39
Radius 40 40
Height, Size, or
40 40 40 40 40 40
Width
Leader Length 40
X Scale Factor or
41 41 41 41 41 41 41
Width
Y Scale Factor or
42 42 42
Bulge
43 Z Scale Factor 43
44 Column Spacing 44
45 Row Spacing 45
Rotation Angle 50 50 50 50 50 50 50
50 Start Angle 50
Curve Fit Tangent 50
End Angle 51
Obliquing Angle 51 51 51 51
51
Angle from
51
Horizontal
62 Color 62 62 62 62 62 62 62 62 62 62 62 62 62 62 62 62
Entities Follow
66 66 66
Flag
70 Dimension Type 70
Vertex or Polyline
70 70
Flag
Attribute Flag 70 70
Column Count 70
- 51 -
Invisible Edges
70
Flag
Text Generation
71 71 71
Flag
71 Row Count 71
Mesh M Vertex
71
Count
Text Justification 72 72 72
72 Mesh N Vertex
72
Count
Field Length 73 73
73 Smooth Surface M
73
Density
Smooth Surface N
74 74
Denstiy
Smooth Surface
75 75
Type
X of Extrusion
210 210 210 210 210 210 210 210 210 210 210 210 210 210
Point
Y of Extrusion
220 210 210 210 210 210 210 210 210 210 210 210 210 210
Point
Z of Extrusion
230 210 210 210 210 210 210 210 210 210 210 210 210 210
Point
The idea for this table was from the book "Inside AutoLisp - Using AutoLisp to Customize AutoCAD" by Joseph Smith and
Rusty Gesner.
- 52 -
The AutoLisp Advanced Tutorial
1/20/03 - Currently working on this. Per visitors request I'll continue where I left off from the Intermediate Tutorials. What
was I thinking?
Let's get started with the Advanced Tutorial. But where? Where do we start? I can't decide. I'm stuck between doing this
and doing that. Back and forth. Back and forth. Hardwired in an unconditional loop. Loop? Aha!
Loops - repeat while
- 53 -
Conditional - cond if
Entities DXF Codes - Line Circle Text Arc PolyLine LWPolyline SPline
Ellipse Solid Trace Block Attribute
Loop Functions :
While Repeat
Example Programs
While
Syntax : (while expression dothis)
expression - Any valid autolisp expression that evaluates to true or non nil.
dothis - Any valid autolisp expression or expressions
Note: No PROGN necessary for multiple expressions like the IF statement.
(while T (princ 1)) returns 1 and keeps returning 1 forever. Your locked into the loop.
(while nil (princ 1)) Exits the loop.
----------------------------------------------------------
(setq cntr 1) setup a counter
(while (< cntr 4) loop until cntr is not less than 4
(princ cntr) print the cntr
(setq cntr(+ cntr 1)) increment the counter
) returns 1 then 2 then 3 and then exits the loop
----------------------------------------------------------
(setq eset(ssget)) returns a selection set
(while (< cntr (sslength eset)) loop through all entities in the selection set
(setq en(ssname eset cntr)) get the entity name of the nth item
- 54 -
(setq enlist(entget en)) get the DXF group codes of the entity
(princ (cdr(assoc 0 enlist))) print the entity type to the command line
) close the while loop
repeat - This function does exactly what you think it would do.
Syntax : (repeat integer)
integer - Any number that is an integer.
Note: No PROGN necessary for multiple expressions like the IF statement.
(repeat 20
(princ "A")
) prints the letter "A" to the command line twenty times
----------------------------------------------------------------------------------------
(setq a 1 b 5) setup some variables.
(repeat 4 repeat these functions 4 times.
(setq a (+ a 1)) add 1 to [a] each loop
(setq b (+ b 5)) add 5 to [b] each loop
) close the loop
(princ a) prints 5 to the command line
(princ b) prints 25 tot he command line
Example Program 1:
(defun C:DrawLines() [define program]
(setq pt1(getpoint "\n First Point: ")) [get first point]
- 55 -
(while (/= nil (setq pt2 (getpoint pt1 "\n Next Point: "))) [get next point]
(command "line" pt1 pt2 "") [draw a line]
(setq pt1 pt2) [set pt1 to last point]
) [close the loop]
) [close the program]
Example Program 2:
(defun C:LetterGuess() define a program
(setq myAnswer "J") set up a variable to hold the answer
(setq yourGuess nil) set up a variable to hold your guess
(while (/= myAnswer yourGuess) while you don't know the answer
(setq yourGuess(getstring "\n Guess what letter: ")) get your guess
) close the loop
) close the program
Example Program 3:
(defun C:PrintVert() define a program
(setq str(getstring "\n Enter a string:")) get a string from the user
(repeat (strlen str) loop once for each character in string
(setq myChar(substr str cntr 1)) get nth character in string
(princ (strcat "\n " myChar)) print a new line then the nth character
) close the loop
) close the program
End of Loop Functions
- 56 -
Conditional Statements:
if cond
Coming soon...
if - This function evaluates an expression to decide which expressions to do afterwards.
Syntax : (if thisIsTrue thenDoThis)
Syntax : (if thisIsTrue thenDoThis elseDoThis)
Syntax : (if thisIsTrue (progn thenDoAllOfThis) (progn elseDoAllOfThis) )
Syntax : (if thisIsTrue (progn thenDoAllOfThis) elseDoThis)
Syntax : (if thisIsTrue thenDoThis (progn elseDoAllOfThis) )
thisIsTrue - Any valid autolisp expression that evaluates to true or non nil.
thenDoThis - Any valid autolisp expression.
elseDoThis - Any valid autolisp expression.
thenDoAllOfThis - Any valid autolisp expressions.
elseDoAllOfThis - Any valid autolisp expressions.
progn - Simply means there will be more than one statement here.
(if T (princ 3)) returns 3
(if T (princ 3)(princ 4)) returns 3 because T always evaluates to True
(if nil (princ 3)(princ 4)) returns 4 because nil always evaluates to False
(if (= nil T) (princ 3)(princ 4)) returns 4 because nil does not equal T
(if (= 3 3) (princ 3) (princ 4)) returns 3
(if (= 3 4) (princ 3) (princ 4)) returns 4
- 57 -
--------------------------------------------------------------------------------------------------
(if (= 3 3)
(progn
(princ 3) returns 3
(princ 5) returns 5
---------------------------------------------------------------------------------------------------
(if (= 3 3)
(progn
(princ 3) returns 3
(princ 5) returns 5
(progn
(princ 8) program never gets inside here because 3 = 3
(princ 9) program never gets inside here because 3 = 3
--------------------------------------------------------------------------------------------------
(if (= 3 4)
(progn
(princ 3) program never gets inside here because 3 does not equal 4
(princ 5) program never gets inside here because 3 does not equal 4
(progn
(princ 8) prints 8
- 58 -
(princ 9) prints 9
cond - This function test conditions until one of them is true. At that point it exits the function.
Syntax : (cond
(ifThisIsTrue thenDoThis)
(elseIfThisIsTrue thenDoThis)
Syntax : (cond
(ifthisIsTrue (progn thenDoAllOfThis) )
(elseIfthisIsTrue (progn thenDoAllOfThis) )
(elseIfthisIsTrue thenDoThis))
(elseIfthisIsTrue (progn thenDoAllOfThis) )
(elseIfthisIsTrue thenDoThis))
thisIsTrue - Any valid autolisp expression that evaluates to true or non nil.
thenDoThis - Any valid autolisp expression.
elseDoThis - Any valid autolisp expression.
thenDoAllOfThis - Any valid autolisp expressions.
elseDoAllOfThis - Any valid autolisp expressions.
progn - Simply means there will be more than one statement here.
- 59 -
(cond
( (= 1 1) (princ "True") ) prints TRUE and exits
( (= 1 2) (princ "True") ) doesn't make it to this point
) returns True
--------------------------------------------------------------------------------------------------
(cond
( (= 1 0) (princ "True") ) skips because 1 does not equal 0
( (= 1 1) (princ "True") ) prints TRUE and exits
( (= 1 2) (princ "True") ) doesn't make it to this point
) returns True
--------------------------------------------------------------------------------------------------
(cond
) returns nil
--------------------------------------------------------------------------------------------------
(cond
( T (princ "Nothing") ) prints "Nothing" because T = True
) returns "Nothing"
--------------------------------------------------------------------------------------------------
(setq a set a variable
- 60 -
(cond
( T (princ "Nothing") ) prints "Nothing" because T = True
) returns "Nothing"
) sets variable [a] to "Nothing"
End of Conditional Statements
Entity DXF Group Code Descriptions For:

Arc Attribute Circle Ellipse
Image Insert / Block Line LWPolyLine
MLine MText Point/Node PolyLine
Solid Text Trace XLine
Note: A good working example of all of these DXF group codes can be found in the CAD2File.lsp program on the AutoLisp
home page. All code is remarked to make it easier to follow along.
Arc
Typical DXF Group Codes for an ARC Entity:
To list an arc entity in AutoCAD you type LIST<enter> and select the arc. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select an Arc: ")))
- 61 -
Would return:
((-1 . <Entity name: 2b80648>) (0 . "ARC") (5 . "89")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 ."AcDbCircle")
(10 1.5 0.5 0.0) (40 . 1.58114) (210 0.0 0.0 1.0) (100 . "AcDbArc")
(50 .5.96143) (51 . 3.46334))
What does all of this garbage mean?
Let's take it apart and put it in order:
(-1 . <Entity name:2b80648>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "ARC") 0 - Entity Type
(5 . "89") 5 - Handle Name (If handles are turned on)
(8 . "STR") 8 - Layer Name
(10 1.5 0.5 0.0) 10 - Center Point
(40 . 1.58114) 40 - Radius
(50 .5.96143) 50 - Start Angle Expressed in Radians
(51 . 3.46334) 51 - End Angle Expressed in Radians
(67 . 0) 67 - Don't worry about this
(100 . "AcDbEntity") 100 - Don't worry about this
(100 ."AcDbCircle") 100 - Don't worry about this
(100 . "AcDbArc") 100 - Don't worry about this Sub Class Marker
(210 0.0 0.0 1.0) 210 - Don't worry about this Extrusion Factor
Let's play with it:
(cdr(assoc 10 enlist)) would return (1.5 0.5 0.0)
Remember, CDR returns everything after the first item in a list.
To get the center point of the arc :
- 62 -
(cdr (assoc 10 enlist))
To get the radius of the arc :
(cdr(assoc 40 enlist))
To get the layer name of the arc :
To get the start angle of the arc :
To get the end angle of the arc :
To see if the entity is indeed an ARC entity :
(if (= "ARC" (cdr(assoc 0 enlist)))
Attribute
This may be a little lengthy. Better grab a cup of joe before getting started.
First off, an attribute is located inside a block entity. This means the entities contained inside a block are called sub-
entities. All entities (Lines, text, attributes, etc.) inside the block are sub-entities. You have to (I'll retract this later) start with
the block entity and step your way into it to find the sub-entities. Kind of like this :
(block entity name (sub-entity name 1) (sub-entity name 2) (sub-entity name 3) SEQEND )
You start with the Block's entity name and step through until you find SEQEND using the ENTNEXT function. I'll get back
to this a little later on.
You have a couple of choices on how to get to the attribute entity inside the block. Now, after I've gone on the record saying
"You have to start at the top and step your way down through the sub-entities using ENTNEXT", I'm going to prove myself
wrong.
The easiest method is using NENTSEL. I have not discussed the NENTSEL function until now. NENTSEL will return the
DXF group code list for a sub-entity inside a block or 3d Polyline. We will stick to blocks for this discussion. You have to
actually pick the attribute sub-entity and not any sub-entity contained inside the block. You can then modify the DXF group
codes and update the attribute. This is fine for single selection and single manipulation of one attribute inside the block. I'll
give a quick demonstration of the NENTSEL function to satisfy those out there that are dying to try it. You know who you
are.
(setq ent(nentsel "\n Select a sub-entity: "))
NENTSEL returns the exact same thing as ENTSEL if the entity selected is not a complex entity like a Block or 3d Polyline.
If you selected acomplex entity such as an attribute inside a block, NENTSEL would return something like this:
- 63 -
(<Entity name: 400a14a8> (5193.24 4935.03 0.0)( (20.0 0.0 0.0) (0.0 20.0 0.0) (0.0 0.0 20.0) (5237.78 4923.46 0.0)) (<Entity
name: 40222278>))
Let's break it down:
(<Entity name: 400a14a8> - The actual entity name of the entity selected.
(5193.24 4935.03 0.0) - The point selected.
( - Start of a four item list
(20.0 0.0 0.0) - We will ignore the Model to World Transformation Matrix
) - End of a four item list
(<Entity name: 40222278>) - The entity name of the block that contains the selected entity
To get the DXF Group codes of the selected attribute using NENTSEL :
(if (setq ent(nentsel "\n Select Attribute: ")) ;- Select the attribute
(progn
(setq en(car ent)) ;- Get the entity name
(setq enlist(entget en)) ;- Get the DXF Group codes
(princ "\n Nothing Selected!") ;- Print message on failure
That's enough on NENTSEL. Let's get back to work finding attribute information. First thing we need to do is let the user
select a block :
(setq ent(entsel "\n Select a block: "))
Then let's get the entity name and dxf group codes of the block:
(setq en(car ent))
- 64 -
Command: !enlist<enter> returns:
((-1 . <Entity name: 40222278>) (0 . "INSERT") (330 . <Entity

name: 40073cf8>) (5 . "85F") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"DELAMINATION") (100 . "AcDbBlockReference") (66 . 1) (2 . "Atl17") (10 5237.78
4923.46 0.0) (41 . 20.0) (42 . 20.0) (43 . 20.0) (50 . 0.0) (70 . 0) (71 . 0)
(44 . 0.0) (45 . 0.0) (210 0.0 0.0 1.0))
Let's take it apart, put it in order, and get rid of the codes that are not needed:
Note: If you want to see the other group codes please see the Insert / Block entity on this page.
(-1 . <Entity name: 40222278>) -1 - Entity name
(0 . "INSERT") 0 - Entity type
(2 . "Atl17") 2 - Name of the block
(10 5237.78 4923.46 0.0) 10 - Insertion Point
(41 . 20.0) 41 - X scale factor
(42 . 20.0) 42 - Y scale factor
(43 . 20.0) 43 - Z scale factor
(50 . 0.0) 50 - Rotation angle
(66 . 1) 66 - Attributes follow flag
Notice the red code. Code number 66. This is the important one for finding attributes. If this code has a value of zero, there
are no attributes in the block. If it has a value of 1, the block contains attributes. Simple! You find the attributes by stepping
through the block using ENTNEXT until you reach the SEQEND entity.
So, how do we do that? Like this:
To get the attribute's DXF group codes:
(if (setq ent(entsel "\n Select a Block: ")) ;- Let the user select a block
(progn
(setq en(car ent)) ;- Get the entity name of the block
(setq enlist(entget en)) ;- Get the DXF group codes
- 65 -
(setq blkType(cdr(assoc 0 enlist))) ;- Save the type of entity
(if (= blkType "INSERT") ;- If the entity type is an Insert entity
(progn
(if(= (cdr(assoc 66 enlist)) 1) ;- See if the attribute flag equals one (if so, attributes follow)
(progn
(setq en2(entnext en)) ;- Get the next sub-entity
(setq enlist2(entget en2)) ;- Get the DXF group codes
(while (/= (cdr(assoc 0 enlist2)) "SEQEND") ;- Start the while loop and keep
;- looping until SEQEND is found.
(princ "\n ") ;-Print a new line
(princ enlist2) ;- Print the attribute DXF group codes
(setq en2(entnext en2)) ;- Get the next sub-entity
(setq enlist2(entget en2)) ;- Get the DXF group codes
) ;- Close the if group code 66 = 1 statement
) ;- Close the if block type = "ATTRIB" statement
) ;- Close the if an Entity is selected statement
Finally we get to see the Attribute DXF group codes which should be printed out on your command line or text screen. They
should look something like this:
((-1 . <Entity name: 40222290>) (0 . "ATTRIB") (330 . <Entity name: 40222278>)

(5 . "862") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 . "TITLETXT_S")
(100 . "AcDbText") (10 5191.7 4940.62 0.0) (40 . 1.6) (1 . "CTSE890") (50 .
0.0) (41 . 1.0) (51 . 0.0) (7 . "arial80") (71 . 0) (72 . 0) (11 0.0 0.0 0.0)
(210 0.0 0.0 1.0) (100 . "AcDbAttribute") (2 . "PROJ") (70 . 0) (73 . 0) (74 .
0))
- 66 -
(
(-1 . <Entity name: 40222290>) -1 - Entity name
(0 . "ATTRIB") 0 - Entity Type
(1 . "CTSE890") 1 - Attribute Value
(2 . "PROJ") 2 - Attribute Tag
(5 . "862") 5 - Handle
(7 . "arial80") 7 - Text Style
(8 . "TITLETXT_S") 8 - Layer name
(10 5191.7 4940.62 0.0) 10 - Insertion Point
(11 0.0 0.0 0.0) 11 - Text alignment point (optional)
(40 . 1.6) 40 - Text Height
(41 . 1.0) 41 - X scale factor (also used for fit text)
(50 . 0.0) 50 - Text Rotation
(51 . 0.0) 51 - Text Oblique Angle
(67 . 0) 67 - Absent or zero = model space / 1 = paper space
(70 . 0) 70 - Attribute flag

0 = No flags
1 = Invisible
2 = Constant
4 = Verification is Required
8 = Preset (no prompt)
(71 . 0) 71 - Text Generation Flag (See text entity)
(72 . 0) 72 - Horiz. Text Justification (See text entity)
(73 . 0) 73 - (See text entity)
(74 . 0) 74 - Vertical Text Justication (See text entity)
(100 . "AcDbEntity") 100 - Ignore
(100 . "AcDbText") 100 - Ignore
(100 . "AcDbAttribute") 100 - Ignore
- 67 -
(210 0.0 0.0 1.0) 210 - Extrusion direction (ignore)
(330 . <Entity name: 40222278>) 330 - Ignore
(410 . "Model") 410 - Layout Tab Name
Let's play with it:
To get the value of the attribute using the program from above:
(cdr(assoc 1 enlist2))
To get the attribute Tag:
(cdr(assoc 2 enlist2))
To change the value of the attribute:
Syntax: (subst new_item old_item entity_list)
(setq newVal (getstring "\n New Attribute value: "))
(setq enlist2 (subst (cons 1 newVal) (assoc 1 enlist2) enlist2))
(entmod enlist2)
(entupd en2)
Phew....I think we got through that unscathed. If you have any questions <Send Email>
Circle
Typical DXF Group Codes for a Circle Entity:
To list a circle in AutoCAD you type LIST<enter> and select the circle. To do this in AutoLisp you would:
(setq en(car(entsel "\n Select a Circle: ")))
Would return:
((-1 . <Entity name: 37b0650>) (0 . "CIRCLE") (5 . "8A")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbCircle")
(10 17.4375 9.6875 0.0) (40 . 1.5) (210 0.0 0.0 1.0))
- 68 -
(-1 . <Entity name: 37b0650>) -1 - AutoCad Entity Name (AutoCAD does this Automatically)
(0 . "CIRCLE") 0 - Entity Type
(5 . "8A") 5 - Handle Name (If handles are turned on)
(10 17.4375 9.6875 0.0) 10 - Center point of circle
(40 . 1.5) 40 - Radius of circle
(67 . 0) Don't worry about this
(100 . "AcDbCircle") Don't worry about this
(100 . "AcDbEntity") Don't worry about this
(210 0.0 0.0 1.0) Don't worry about this
Let's play with it:
To get the radius of the circle :
To get the center of the circle :
To get the layer name of the circle :
To see if the entity is indeed a CIRCLE entity :
(if (= "CIRCLE" (cdr(assoc 0 enlist)))
Ellipse
Typical DXF Group Codes for an ELLIPSE Entity:
To list an ellipse entity in AutoCAD you type LIST<enter> and select the ellipse. To do this in AutoLisp you would:
- 69 -
(setq en(car (entsel "\n Select an Ellipse :")))
Would return:
( (-1 . <Entity name: 1cb0670>) (0 . "ELLIPSE") (5 . "86")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbEllipse")
(10 3.0 3.0 0.0) (11 21.2132 -21.2132 0.0) (210 0.0 0.0 1.0)
(40 . 0.0471405) (41 . 0.0) (42 . 6.28319) )
(-1 . <Entity name:1cb0670>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "ELLIPSE") 0 - Entity Type
(10 3.0 3.0 0.0) 10 - Center Point
(11 21.2132 -21.2132 0.0) 11 - end Point of Major axis (relative to center)
(40 . 0.0471405) 40 - Ratio of Minor axis to Major axis
(41 . 0.0) 41 - Start Parameter (Equals 0.0 for closed ellipse)
(42 . 6.28319) 42 - End Parameter (Equals 2 * pi for closed ellipse)
(67 . 0) 67 - Absent or zero indicates the entity is in

model space. If set to 1, paper space.
(100 ."AcDbEllipse") 100 - Don't worry about this
Let's play with it:
To get the center point of the ellipse :
- 70 -
To get the length of the major axis :
;;;--- Save the center point of the ellipse

(setq centerPt(cdr(assoc 10 enlist)))
;;;--- Save the endPoint of the major axis relative to center pt

(setq endPt(cdr(assoc 11 enlist)))
;;;--- Create a new point on the end of the major axis
;;; by subtracting code 10 point from code 11 point

(setq newPt
(list
(- (car centerPt)(car endPt))
(- (cadr centerPt)(cadr endPt))
)
)
;;;--- Finally, find the major axis length

(setq majorAxisLength(* 2.0 (distance centerPt newPt)))
To get the length of the minor axis :
(* majorAxisLength (cdr(assoc 40 enlist)))
Note: See example above for majorAxisLength
To see if the entity is indeed an Ellipse entity :
(if (= "ELLIPSE" (cdr(assoc 0 enlist)))
Image
To list an image entity in AutoCAD you type LIST<enter> and select the image. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select an Image :")))

Would return some garbage like this:
((-1 . <Entity name: 40073da8>) (0 . "IMAGE") (330 . <Entity

name: 40073cf8>) (5 . "4D") (100 . "AcDbEntity") (410 . "Model") (8 . "0") (100 .
"AcDbRasterImage") (90 . 0) (10 9.00868 6.59115 0.0) (11 0.0012987
0.0 0.0) (12 7.95199e-020 0.0012987 0.0) (13 770.0 559.0 0.0) (340 . <Entity
name: 40073d98>) (70 . 7) (280 . 0) (281 . 50) (282 . 50) (283 . 0) (360 .
<Entity name: 40073da0>) (71 . 1) (91 . 2) (14 -0.5 -0.5 0.0) (14 769.5 558.5
0.0))
- 71 -
(-1 . <Entity name: 40073da8>) -1 Entity Name (AutoCAD Automatically takes care of this)
(0 . "IMAGE") 0 - Entity Type
(5 . "4D") 5 - Handle Name (If handles are turned on)
(8 . "0") 8 - Layer Name
(10 9.00868 6.59115 0.0) 10 - Insertion Point
(11 0.0012987 0.0 0.0) 11 - U-vector of a single pixel (points along the visual bottom
of the image, starting at the insertion point) (in OCS)
(12 7.95199e-020 0.0012987 0.0) 12 - V-vector of a single pixel (points along the visual left
of the image, starting at the insertion point) (in OCS)
(13 770.0 559.0 0.0) 13 - Image size in pixels
(14 -0.5 -0.5 0.0) 14 - Clip boundary vertex (in OCS)

1 . For rectangular clip boundary type, two opposite
corners must be specified. Default is (-0.5,-0.5),
(size.x-0.5, size.y-0.5).
2 . For polygonal clip boundary type, three or more
vertices must be specified. Polygonal vertices must be
listed sequentially.
(14 769.5 558.5 0.0) 14 - Other corner for rectangular. See (1) above.
(70 . 7) 70 - Image display properties (Can be added together)

1. Show Image
2. Show image when not aligned with screen.
4. Use clipping boundary
8. Transparency is on.
With a value of 7 it is using 1, 2, & 4
(71 . 1) 71 - Clipping boundary type. 1= Rectangular 2=Polygonal
(90 . 0) 90 - Class Version
(91 . 2) 91 - Number of clip boundary vertices that follow.
(330 . <Entity name: 40073cf8>) 330 - Ignore
(100 . "AcDbRasterImage") 100 - Ignore
(280 . 0) 280 - Clipping state 0=Off 1=On
(281 . 50) 281 - Brightness Value 0 to 100 (Default = 50)
- 72 -
(282 . 50) 282 - Contract Value 0 to 100 (Default = 50)
(283 . 0) 283 - Fade Value 0 to 100 (Default = 0)
(340 . <Entity name: 40073d98>) 340 - Ignore Hard reference to imagedef object
(360 . <Entity name: 40073da0>) 360 - Ignore Hard reference to imagedef_reactor object
(410 . "Model") 410 - Layout tab name
Let's play with it:
To get the insertion point of the image :
To get the image size in pixels :
(setq x(car(cdr(assoc 13 enlist))))
(setq y(cadr(cdr(assoc 13 enlist))))
To get the layer name of the image :
To get the layout Tab name :
Insert / Block
Typical DXF Group Codes for an INSERT Entity:
To list an insert entity in AutoCAD you type LIST<enter> and select the block. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a block :")))

Would return:
((-1 . <Entity name: 1c90970>) (0 . "INSERT") (5 . "EB6")

(100 . "AcDbEntity") (67 . 0) (8 . "TX") (100 . "AcDbBlockReference")
(2 . "HR") (10 1.5 0.5 0.0) (41 . 1.0) (42 . 1.0) (43 . 1.0) (50 . 0.0)(70 . 0)
(71 . 0) (44 . 0.0) (45 . 0.0) (210 0.0 0.0 1.0))
- 73 -
(-1 . <Entity name:1c90970>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "INSERT") 0 - Entity Type
(1 . "PATH") 1 - Xref path name
Note: GROUP CODE 1 is optional.

It is present only if the block is an xref.
(2 . "HR") 2 - Name of Block
(5 . "EB6") 5 - Handle Name (If handles are turned on)
(8 . "TX") 8 - Layer Name
(10 1.5 0.5 0.0) 10 - Insertion Point
(41 . 1.0) 41 - X Scale Factor. Optional, 1 = default
(42 . 1.0) 42 - Y Scale Factor. Optional, 1 = default
(43 . 1.0) 43 - Z Scale Factor. Optional, 1 = default
(44 . 0.0) 44 - Don't worry about this. Optional.
(45 . 0.0) 45 - Don't worry about this. Optional.
(50 .5.96143) 50 - Rotation Angle Expressed in Radians
(66 . 0) 66 - Flag meaning attributes follow. Optional.
0 = Default
1 = Attributes-follow flag
A series of attribute entities is expected to follow the insert,
terminated by a SEQEND entity.

(70 . 0) 70 - Flag See the following:
Block flags:
0 = Normal
1 = This is an anonymous block generated by hatching,
associative dimensioning, other internal operations,
or an application
2 = This block has attribute definitions
4 = This block is an external reference (xref)
- 74 -
8 = This block is an xref overlay
16 = This block is externally dependent
32 = This is a resolved external reference,
or dependent of an external reference
(ignored on input)
64 = This definition is a referenced external reference
(ignored on input)
Note: Block flags may be combined. For instance,

a 70 DXF group code of 6 would mean the block
has attributes (code 2) and is an external
reference (code 4). Because 2 + 4 = 6
(71 . 0) 71 - Don't worry about this.
(100 ."AcDbBlockReference") 100 - Don't worry about this
(210 0.0 0.0 1.0) 210 - Don't worry about this Extrusion Direction
Let's play with it:
To get the insertion point of the block :
To get the name of the block :
To get the layer name of the block :
To get the group 70 block flag :
To get the X scale factor of the block :
To see if the entity is indeed a BLOCK entity :
(if (= "INSERT" (cdr(assoc 0 enlist)))
- 75 -
Line
Typical DXF Group Codes for a LINE Entity:
To list a line in AutoCAD you type LIST<enter> and select the line. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a Line: ")))
Would return:
((-1 . Entity name: 37b0648) (0 ."LINE") (5 . "89")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbLine")
(10 9.0 7.9375 0.0) (11 11.1213 10.0588 0.0) (210 0.0 0.0 1.0))
(-1 . Entity name: 37b0648) -1 - AutoCad Entity Name (AutoCAD does this Automatically)
(0 ."LINE") 0 - Entity Type
(5 . "89") 69 - Handle name (if handles are turned on)
(8 . "STR") 8 - Name of Layer
(10 9.0 7.9375 0.0) 10 - Start Point of Line
(11 11.1213 10.0588 0.0) 11 - End Point of Line
(100 . "AcDbLine") Don't worry about this SubClass Marker.
(210 0.0 0.0 1.0) Don't worry about this. This is default unless extruded.
I'll bet AutoCad doesn't look so mysterious anymore. Does it?
Let's play with it:
To get the length of the line we need the distance from the start point to the end point :
- 76 -
(distance (cdr (assoc 10 enlist)) (cdr(assoc 11 enlist)) )
To get the angle of the line we need two points. The start point and the end point :
(angle (cdr(assoc 10 enlist)) (cdr(assoc 11 enlist)) )
To get the layer name of the line :
To see if the entity is indeed a LINE entity :
(if (= "LINE" (cdr(assoc 0 enlist)))
LWPolyLine
Typical DXF Group Codes for an LWPOLYLINE Entity:
To list an polyline entity in AutoCAD you type LIST<enter> and select the polyline. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a Polyline :")))
Would return:
((-1 . <Entity name: 1cb0658>) (0 . "LWPOLYLINE") (5 . "83")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbPolyline")(90 . 5) (70 . 0)
(43 . 0.0) (38 . 0.0) (39 . 0.0) (10 1.0 1.0) (40 . 0.0) (41 . 0.0) (42 . 0.0) (10
2.0 1.0) (40 . 0.0) (41 . 0.0) (42 . 0.0) (10 2.0 2.0) (40 . 0.0) (41 . 0.0) (42 .
0.0) (10 3.0 3.0) (40 . 0.0) (41 . 0.0) (42 . 0.0) (10 1.0 4.0) (40 . 0.0) (41 .
0.0) (42 . 0.0) (210 0.0 0.0 1.0))
(-1 . <Entity name:1cb0658>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "LWPOLYLINE") 0 - Entity Type
(38 . 0.0) 38 - Elevation (optional) Default = 0.0
(39 . 0.0) 39 - Thickness (optional) Default = 0.0
NOTE:
- 77 -
The next series of codes are Vertex points (group 10 codes) followed by group 40 codes.
These codes always appear in the list by order in which they were created.
10 - Vertex 2D point
40 - Starting Width of the polyline. This is optional. Default = 0.
Code 40 is not used if group code 43 is set.
41 - Ending Width of the polyline. This is optional. Default = 0.
Code 41 is not used if group code 43 is set.
42 - Bulge factor. Used to create arcs in the polyline.
43 - Constant Width. Optional. Default = 0.
Code 43 is not used if codes 40 and 41 are set.
(10 1.0 1.0) 10 - First Vertex (Start Point)

(40 . 0.0) 40 - First Vertex Starting Width
(41 . 0.0) 41 - First Vertex Ending Width
(42 . 0.0) 42 - First Vertex Bulge Factor
(10 2.0 1.0) 10 - Second Vertex Point

(40 . 0.0) 40 - Second Vertex Starting Width
(41 . 0.0) 41 - Second Vertex Ending Width
(42 . 0.0) 42 - Second Vertex Bulge Factor
(10 2.0 2.0) 10 - Next Vertex Point

(40 . 0.0) 40 - Next Vertex Starting Width
(41 . 0.0) 41 - Next Vertex Ending Width
(42 . 0.0) 42 - Next Vertex Bulge Factor
(10 3.0 3.0) 10 - Next Vertex Point

(40 . 0.0) 40 - Next Vertex Starting Width
(41 . 0.0) 41 - Next Vertex Ending Width
(42 . 0.0) 42 - Next Vertex Bulge Factor
(10 1.0 4.0) 10 - Last Vertex Point

(40 . 0.0) 40 - Last Vertex Starting Width
(41 . 0.0) 41 - Last Vertex Ending Width
(42 . 0.0) 42 - Last Vertex Bulge Factor
(43 . 0.0) 43 - Constant Width

(70 . 0) 70 - Polyline Flag. See below.
FLAGS:
0 - Default
1 - Closed
128 - PLINEGEN (Generation of LineType)
(90 . 5) 90 - Number of vertices
- 78 -
(100 ."AcDbPolyline") 100 - Don't worry about this
Let's play with it:
To get the start point of the LWPolyline :
Unfortunately, that is as far down as you can dig into the list. To get all of the group 10 codes,
you will have to manually search for them.
Here's an example:
(setq myVertexList(list)) ;create an empty list to store the vertices in.
(foreach a enlist ;;;--- step through each sub-list

(if(= 10 (car a)) ;;;--- if the first item in the sub-list equals 10 then
(setq myVertexList ;;;--- reset myVertexList to
(append myVertexList ;;;--- the old vertex list
(list ;;;--- plus a list containing
(cdr a) ;;;--- the vertex point
) ;;;--- close the list statement
) ;;;--- close the append statement
) ;;;--- close the setq statement
) ;;;--- close the if statement
) ;;;--- close the foreach statement
This would return:
( (1.0 1.0) (2.0 1.0) (2.0 2.0) (3.0 3.0) (1.0 4.0) )
A list of every vertex! Cool.
To get the layer name of the LWPolyline :
To see if the entity is indeed a LWPolyline entity :
(if (= "LWPOLYLINE" (cdr(assoc 0 enlist)))

(princ "\n It is a LWPolyLine")
- 79 -
(princ "\n It is not a LWPolyLine")
)
MLine
Typical DXF Group Codes for a MLine Entity:
To list a MLine in AutoCAD you type LIST<enter> and select the MLine. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select an MLine: ")))
Would return something like this :
((-1 . <Entity name: 40222978>) (0 . "MLINE") (330 . <Entity

name: 40073cf8>) (5 . "92F") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"0") (100 . "AcDbMline") (2 . "STANDARD") (340 . <Entity name: 40073cc0>) (40 .
1.0) (70 . 0) (71 . 3) (72 . 4) (73 . 2) (10 11.4446 15.392 0.0) (210 0.0 0.0
1.0) (11 11.4446 15.392 0.0) (12 1.0 0.0 0.0) (13 0.690073 0.72374 0.0) (74 .
2) (41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.38171) (41 . 0.0) (75 . 0)
(11 30.3875 15.392 0.0) (12 0.0 1.0 0.0) (13 -0.707107 0.707107 0.0) (74 . 2)
(41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.41421) (41 . 0.0) (75 . 0) (11
30.3875 31.4532 0.0) (12 -1.0 0.0 0.0) (13 -0.707107 -0.707107 0.0) (74 . 2)
(41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.41421) (41 . 0.0) (75 . 0) (11
10.6793 31.4532 0.0) (12 0.0475993 -0.998867 0.0) (13 0.72374 -0.690073 0.0)
(74 . 2) (41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.44912) (41 . 0.0) (75
. 0))
(-1 . <Entity name: 40222978>) -1 - Entity Name
(0 . "MLINE") 0 - Entity Type
(2 . "STANDARD") 2 - Style (Must exist in MLineStyle Dictionary)
(5 . "92F") 5 - Handle (If handles are turned on)
(8 . "0") 8 - Layer Name
(40 . 1.0) 40 - Scale Factor

(70 . 0) 8 - Justification: 0 = Top, 1 = Zero, 2 = Bottom
- 80 -
(71 . 3) 71 - Flags - 1=Unlocked 2=Closed
4=Suppress start caps 8=Suppress end caps.
(72 . 4) 72 - Number of vertices
(73 . 2) 73 - Number of elements in MLineStyle Definition
(10 11.4446 15.392 0.0) 10 - Start Point
------------------------------------- Start the Vertex Loop -------------------------------------
Note: Each vertex will have a code 11, 12, 13, 74, 41, and 75. I'm going to include the first appearance of codes 12, 13,
74, and 75 and delete the rest for clarity. I'll explain later.
(11 11.4446 15.392 0.0) 11 - First Vertex point of multiple entries
(12 1.0 0.0 0.0) 12 - Direction Vector for next line from this point
(13 0.690073 0.72374 0.0) 13 - Direction Vector of miter at this vertex
(74 . 2) 74 - Number of group 41's to follow (I'll explain later)
(41 . 0.0) 41 - First code 41
(41 . 0.0) 41 - Second code 41
(75 . 0) 75 - Number of group 42's to follow (fill parameters)
(11 30.3875 15.392 0.0) 11 - Second vertex point
(12 0.0 1.0 0.0) 12 - Second Direction vector for next line
(13 -0.707107 0.707107 0.0) 13 - Second Direction for miter
(11 30.3875 31.4532 0.0) 11 - Third vertex point
(12 -1.0 0.0 0.0) 12 - Third Direction vector for next line
(13 -0.707107 -0.707107 0.0) 13 - Third Direction for miter
(11 10.6793 31.4532 0.0) 11 - Fourth vertex point
(12 0.0475993 -0.998867 0.0) 12 - Fourth Direction vector for next line
(13 0.72374 -0.690073 0.0) 13 - Fourth Direction for miter
(100 . "AcDbMline") 100 - Ignore this subclass marker
(210 0.0 0.0 1.0) 210 - Ignore extrusion direction
- 81 -
(340 . <Entity name: 40073cc0>) 340 - Ignore (needed to modify MLineStyle. See note below.
(410 . "Model") 410 - Layout Tab Name
Notes: From the book...
The group code 41 may contain zero or more items. The first group code 41 value is the distance from the segment vertex
along the miter vector to the point where the line element's path intersects the miter vector. The next group code 41 value is
the distance along the line element's path from the point defined by the first group 41 to the actual start of the line element.
The next is the distance from the start of the line element to the first break (or cut) in the line element. The successive group
code 41 values continue to list the start and stop points of the line element in this segment of the mline. Linetypes do not affect
group 41 lists.
The 2 group codes in mline entities and mlinestyle objects are redundant fields. These groups should not be modified under
any circumstances, although it is safe to read them and use their values. The correct fields to modify are as follows:
Mline - The 340 group in the same object, which indicates the proper MLINESTYLE object.
Mlinestyle -The 3 group value in the MLINESTYLE dictionary which precedes the 350 group that has the handle or entity
name of the current mlinestyle.
Here's an example of how to get all of the vertices in a list:
(setq en(car(entsel "\n Select a MLine: "))) ;;;--- Get the entity name
(setq enlist(entget en)) ;;;--- Get the dxf group codes
(setq myVertexList(list)) ;;;--- create an empty list to store the vertices in.
(setq v1(cdr(assoc 10 enlist))) ;;;--- Get the starting point of the mline
(setq myVertexList(append myVertexList (list v1))) ;;;--- Add the point to the list
(foreach a enlist ;;;--- step through each sub-list

(if(= 11 (car a)) ;;;--- if the first item in the sub-list equals 11 then
(setq myVertexList ;;;--- reset myVertexList to
(append myVertexList ;;;--- the old vertex list
(list ;;;--- plus a list containing
(cdr a) ;;;--- the vertex point
) ;;;--- close the list statement
) ;;;--- close the append statement
) ;;;--- close the setq statement
) ;;;--- close the if statement
) ;;;--- close the foreach statement
This would return:
- 82 -
( (11.4446 15.392 0.0) (11.4446 15.392 0.0)(30.3875 15.392 0.0)(30.3875 31.4532 0.0)
(10.6793 31.4532 0.0) )
A list of every vertex! Cool.
Extra.......Let's redraw the MLine with Lines:
(command "line" (car myVertexList)) ;;;--- Start the line command with the first vertex
(foreach a (cdr myVertexList) ;;;--- Cycle through the rest of the vertex list
(command a) ;;;--- Send the vertex to the line command
(command) ;;;--- End the line command
MText
Typical DXF Group Codes for an MText Entity:
To list MText in AutoCAD you type LIST<enter> and select the MText. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select MText: ")))

Would return:
((-1 . <Entity name: 40222a10>) (0 . "MTEXT") (330 . <Entity name: 40073cf8>) (5 . "942") (100 . "AcDbEntity") (67 . 0)
(410 . "Model") (8 . "0") (100 . "AcDbMText") (10 37.2758 63.7667 0.0) (40 . 0.2) (41 . 54.9151) (71
. 1) (72 . 5) (1 . "This is an Mtext string. ") (7 . "Standard") (210 0.0 0.0 1.0) (11 1.0 0.0 0.0) (42 . 4.2) (43 . 0.266667) (50 .
0.0) (73 . 1) (44 . 1.0))
(-1 . <Entity name: 40222a10>) -1 - Entity Name
(0 . "MTEXT") 0 - Entity Type
(1 . "This is an Mtext string. ") 1 - Text Value (See Note 1 and 2 Below!!!)
(5 . "942") 5 - Handle (If handles are turned on)
(7 . "Standard") 7 - Text Style
(8 . "0") 8 - Layer Name
- 83 -
(10 37.2758 63.7667 0.0) 10 - Insertion Point
(11 1.0 0.0 0.0) 11 - X Axis Direction Vector
(40 . 0.2) 40 - Initial Text Height
(41 . 54.9151) 41 - Reference Rectangle Width
(42 . 4.2) 42 - Horizontal width of the characters (Ignored)
(43 . 0.266667) 43 - Vertical Height of the MText entity (Ignored)
(44 . 1.0) 44 - Line Spacing factor (Optional)
(50 . 0.0) 50 - Rotation angle (Always in radians)

(71 . 1) 71 - Attachment point 1=Top 2=Top Center

3= Top Right 4=Middle Left 5=Middle Center
6=Middle Right 7=Bottom Left 8= Bottom Center
9=Bottom Right
(72 . 5) 72 - Drawing Direction 1 = Left to Right

3 = Top to Bottom
5 = Use Text Style Default
(73 . 1) 73 - Line Spacing Style

1 = At Least (Taller characters will override)
2 = Exact (Taller characters will not override)
(100 . "AcDbMText") 100 - Ignore
(210 0.0 0.0 1.0) 210 - Extrusion direction (Ignore)
(410 . "Model") 410 - Tab Layout Name
NOTE 1 : Formatting!
MText can contain formatting characters. For instance, if I change the MText entity we used in the example above:
(1 . "This is an Mtext string. ")
to use the Arial font, underlined, and bold, the MText value would look something like this:
- 84 -
(1 . "{\\fArial|b1|i0|c0|p34;\\LThis is an Mtext string. \\Ftxt.shx; }")
Not very pretty is it?
Mtext formatting codes:
Format code Purpose

\0...\o Turns overline on and off
\L...\l Turns underline on and off
\~ Inserts a nonbreaking space
\\ Inserts a backslash
\{...\} Inserts an opening and closing brace
\File name; Changes to the specified font file
\Hvalue; Changes to the text height specified in drawing units
\Hvaluex; Changes the text height to a multiple of the current text height
\S...^...; Stacks the subsequent text at the \, #, or ^ symbol
\Tvalue; Adjusts the space between characters, from.75 to 4 times
\Qangle; Changes obliquing angle
\Wvalue; Changes width factor to produce wide text
\A Sets the alignment value; valid values: 0, 1, 2 (bottom, center, top)
Note: Use curly braces ({ }) to apply a format change only to the text within the braces. You can nest braces up to eight levels
deep.
NOTE 2 : String Length!
If the number of characters in an MText entity is less than 250, all characters will be in group code number 1. If you exceed
249 characters, the characters are broken up in 250 character chunks and placed under group code number 3. The remainder
of the characters will be in group code 1. For instance, if I change the MText entity we used in the example above:
(1 . "This is an Mtext string. ")
into a string that is 600 characters long, the MText value would look something like this:
(1 .
"1234567899123456789012345678911234567892123456789312345678941234567895123456789
61234567897123456789812345678991234567890 ")
Where's the rest of the string? It is stored in the group 3 codes. There are two if them that are 250 characters each.
(3 .
"1234567890123456789112345678921234567893123456789412345678951234567896123456789
71234567898123456789912345678901234567891123456789212345678931234567894123456789
51234567896123456789712345678981234567899123456789012345678911234567892123456789
31234567894")
(3 .
"1234567895123456789612345678971234567898123456789912345678901234567890123456789
11234567892123456789312345678941234567895123456789612345678971234567898123456789
91234567890123456789112345678921234567893123456789412345678951234567896123456789
71234567898")
To put the string back together, you would have to use the STRCAT function on the group 3 codes first:
- 85 -
(setq myStr "")
(setq en(car(entsel "\n Select Mtext: ")))
(foreach a enlist
(if (= 3 (car a))
(setq myStr (strcat myStr (cdr a)))
Then you would have to tack the string stored in group code 1 to the end. Like this:
(setq myStr(strcat myStr (cdr(assoc 1 enlist))))
Let's play with it:
To get the initial height of the MText :
To get the insertion :
To get the layer name of the MText :
To get the text value of the MText :
(cdr(assoc 1 enlist)) ;if it less than 250 characters long (See Note 1 Above)
To get the rotation angle of the MText :
To see if the entity is indeed a MText entity :
- 86 -
(if (= "MTEXT" (cdr(assoc 0 enlist)))
Point / Node
Typical DXF Group Codes for an Point or Node Entity:
To list a point entity in AutoCAD you type LIST<enter> and select the point. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a Point: ")))

Would return:
((-1 . <Entity name: 4009ff78>) (0 . "POINT") (330 . <Entity

name: 40073cf8>) (5 . "267") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"0") (100 . "AcDbPoint") (10 4.27913 8.26876 0.0) (210 0.0 0.0 1.0) (50 . 0.0))
(-1 . <Entity name: 4009ff78>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "POINT") 0 - Entity Type
(8 . "0") 8 - Layer Name
(10 4.27913 8.26876 0.0) 10 - Insertion Point
(50 . 0.0) 50 - Angle of the X axis for the UCS in effect when the point
was drawn if PdMode does not = 0 (default = 0)

(100 . "AcDbPoint") 100 - Ignore
(210 0.0 0.0 1.0) 210 - Ignore extrusion direction
(410 . "Model") 410 - Layout tab name
- 87 -
Let's play with it:
To get the insertion point of the Point :
(cdr (assoc 10 enlist)) would return : (4.27913 8.26876 0.0)
There's not a lot of data associated with a point!
Polyline
Typical DXF Group Codes for a Polyline Entity:
To list a polyline entity in AutoCAD you type LIST<enter> and select the polyline. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a PolyLine: ")))

Would return:
((-1 . <Entity name: 40222a38>) (0 . "POLYLINE") (330 . <Entity

name: 40073cf8>) (5 . "947") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"0") (100 . "AcDb2dPolyline") (66 . 1) (10 0.0 0.0 0.0) (70 . 4) (40 . 0.0) (41
. 0.0) (210 0.0 0.0 1.0) (71 . 0) (72 . 0) (73 . 0) (74 . 0) (75 . 6))
(-1 . <Entity name: 40222a38>) -1 - Entity Name
(0 . "POLYLINE") 0 - Entity Type
(5 . "947") 5 - Handle (If handles are turned on.)
(8 . "0") 8 - Layer Name
(10 0.0 0.0 0.0) 10 - Always Zero
(40 . 0.0) 40 - Default Start Width (Default = 0)
(41. 0.0) 41 - Default End Width (Default = 0)
(66 . 1) 66 - Vertices follow flag (Always 1 for Polylines)

- 88 -
(70 . 4) 70 - PolyLine flag
0 = Default (No flags) 1 = This is a closed polyline or mesh closed in
M direction. 2 = Curve fit Vertices have been added
4 = Spline fit Vertices have been added
8 = This is a 3D Polyline
16 = This is a 3D polygon Mesh
32 = This polygon Mesh is Closed in the N Direction
64 = This polygon is a polygon Mesh
128 = Generate Line Type Continuously around Vertices
(71 . 0) 71 - Polygon mesh M vertex count (Optional)
(72 . 0) 72 - Polygon mesh N vertex count (Optional)
(73 . 0) 73 - Smooth Surface M Density (Optional)
(74 . 0) 74 - Smooth Surface N Density (Optional)
(75 . 6) 75 - Curves and Smooth Surface type (Optional)

0 = No Smooth Surface Fitted
5 = Quandratic B-Spline Surface
6 = Cubic B-Spline Surface
8 = Bezier Surface
(100 . "AcDb2dPolyline") 100 - Ignore
(210 0.0 0.0 1.0) 210 - Extrusion Direction (Ignore)
(410 . "Model") 410 - Tab Layout Name
Notice there are no vertices shown. You have to step through this entity looking at the sub-entities for the vertices until you
come across the SEQEND entity. Sound familar? It should. This is exactly like the Attribute Entity. Pretty much anyway.
Please read the Attribute section above for instructions on the ENTNEXT function used to step into an entity looking for sub-
entities and the SEQEND entity definition. When you get through, come back to here.
So, we now know how to step into an entity. Let's do that for this polyline and save a list of all of the vertices.
(defun C:PTEST()
;;;--- Get the entity's name

(setq en(car(entsel "\n Select a PolyLine: ")))
;;;--- Get the DXF group codes of the entity

;;;--- Create an empty list to hold the points

(setq ptList(list))
- 89 -
;;;--- Get the sub-entities name
(setq en2(entnext en))
;;;--- Get the dxf group codes of the sub-entity

(setq enlist2(entget en2))
;;;--- While the polyline has a next vertice

(while (not (equal (cdr(assoc 0 (entget(entnext en2))))"SEQEND"))
;;;--- Get the next sub-entity

(setq en2(entnext en2))
;;;--- Get its dxf group codes

(setq enlist2(entget en2))
;;;--- Check to make sure it is not a spline reference point

(if(/= 16 (cdr(assoc 70 enlist2)))
;;;--- It is a vertex, save the point in a list [ptlist]

(setq ptList(append ptList (list (cdr(assoc 10 enlist2)))))
)
)
(princ)
)
If you run this program and then type this in the command line:
Command: ptList!<enter>
It will return a list of all of the vertices and will look something like this:
((48.4773 56.3423 0.0) (47.9891 57.1226 0.0) (47.7463 57.7535 0.0) (47.7072
58.2456 0.0) (47.8304 58.6095 0.0) (48.0741 58.8559 0.0) (48.3968 58.9954 0.0)
(48.7568 59.0385 0.0) (49.1125 58.9959 0.0) (49.4264 58.8788 0.0) (49.6767
58.7011 0.0) (49.8457 58.4773 0.0) (49.9157 58.2219 0.0) (49.869 57.9495 0.0)
(49.688 57.6745 0.0) (49.355 57.4114 0.0) (48.8522 57.1748 0.0))
Let's play with it:
Let's get the start point of the polyline from the point list:
(setq startPt(car ptList))
Let's get the end point of the polyline from the point list:
(setq endPt(car(reverse ptList)))
Let's get the area and perimeter of the polyline:
(command "area" "Object" en)

(setq plineArea(getvar "area"))
(setq plinePeri(getvar "perimeter"))
- 90 -
Let's get the Line Type of the polyline:
(if(cdr(assoc 6 enlist))
(setq plineLtyp(cdr(assoc 6 enlist)))
(setq plineLtyp "BYLAYER")
)
Let's get the Color of the polyline:
(if(cdr(assoc 62 enlist))
(setq plineClr(cdr(assoc 62 enlist)))
(setq plineClr "BYLAYER")
)
Solid
Typical DXF Group Codes for an SOLID Entity:
To list a solid entity in AutoCAD you type LIST<enter> and select the solid. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a Solid: ")))

Would return:
((-1 . <Entity name: 1cb06d0>) (0 . "SOLID") (5 . "92")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbTrace")
(10 1.0 1.0 0.0) (11 2.0 1.0 0.0) (12 3.0 3.0 0.0) (13 4.0 4.0 0.0)
(39 . 0.0) (210 0.0 0.0 1.0))
(-1 . <Entity name:2b80648>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "SOLID") 0 - Entity Type
(10 1.0 1.0 0.0) 10 - First Corner Point
(11 2.0 1.0 0.0) 11 - Second Corner Point
(12 3.0 3.0 0.0) 12 - Third Corner Point
(13 4.0 4.0 0.0) 13 - Fourth Corner Point
Note: If only three corners are used to define the solid,

corner 4 will equal corner 3.
- 91 -
(39 . 0.0) 39 - Thickness. (optional) Default = 0.0

(100 ."AcDbTrace") 100 - Don't worry about this
Let's play with it:
To get the first corner of the solid :
To get the second corner of the solid :
To get the layer name of the solid :
To see if the entity is indeed a SOLID entity :
(if (= "SOLID" (cdr(assoc 0 enlist)))
Text
Typical DXF Group Codes for a Text Entity:
To list a text entity in AutoCAD you type LIST<enter> and select the text. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a Text Entity: ")))
Would return:
((-1 . <Entity name: 37b0658>) (0 . "TEXT") (5 . "8B") (100 . "AcDbEntity")

(67 . 0) (8 . "STR") (100 . "AcDbText") (10 23.4375 9.1875 0.0) (40 . 0.125)
(1 . "This is some Text!") (50 . 0.0) (41 . 1.0) (51 . 0.0) (7 . "STANDARD")
- 92 -
(71 . 0) (72 . 0) (11 0.0 0.0 0.0) (210 0.0 0.0 1.0) (100 . "AcDbText")
(73 . 0))
(-1 . <Entity name: 37b0658>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "TEXT") 0 - Entity Type
(1 . "This is some Text!") 1 - Text Value
(5 . "8B") 5 - Handle Name (If handles are turned on)
(7 . "STANDARD") 7 - Text Style Name
(10 23.4375 9.1875 0.0) 10 - Start Point for the text entity
(11 0.0 0.0 0.0) Don't worry about this
(40 . 0.125) 40 - Text Height
(41 . 1.0) Don't worry about this width factor.
(50 . 0.0) 50 - Rotation Angle expressed in radians
(51 . 0.0) Don't worry about this oblique angle.
(71 . 0) 0=Normal 2=Backward 4=Upside Down
(72 . 0) Don't worry about this. 72 and 73 work together for alignment.
(73 . 0) Don't worry about this. 72 and 72 work together for alignment.
(100 . "AcDbText") Don't worry about this SubClass Marker
(210 0.0 0.0 1.0) Don't worry about this Extrusion Factor.
Let's play with it:
- 93 -
To get the height of the text :
To get the start point of the text :
To get the layer name of the text :
To get the text value of the text :
To get the rotation angle of the text :
To see if the entity is indeed a TEXT entity :
(if (= "TEXT" (cdr(assoc 0 enlist)))
Trace
Typical DXF Group Codes for a TRACE Entity:
To list a trace entity in AutoCAD you type LIST<enter> and select the trace. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select a TRACE:")))

Would return:
((-1 . <Entity name: 1cb06f8>) (0 . "TRACE") (5 . "97")

(100 . "AcDbEntity") (67 . 0) (8 . "STR") (100 . "AcDbTrace")
(10 2.0 2.5 0.0) (11 2.0 1.5 0.0) (12 4.0 2.5 0.0) (13 4.0 1.5 0.0)
(39 . 0.0) (210 0.0 0.0 1.0))
(-1 . <Entity name:1cb06f8>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "TRACE") 0 - Entity Type
- 94 -
(10 2.0 2.5 0.0) 10 - First Corner Point
(11 2.0 1.5 0.0) 11 - Second Corner Point
(12 4.0 2.5 0.0) 12 - Third Corner Point
(13 4.0 1.5 0.0) 13 - Fourth Corner Point
(39 . 0.0) 39 - Thickness. (optional) Default = 0.0

(100 ."AcDbTrace") 100 - Don't worry about this
Let's play with it:
To get the first corner of the trace :
To get the second corner of the trace :
To get the layer name of the trace :
To see if the entity is indeed a TRACE entity :
(if (= "TRACE" (cdr(assoc 0 enlist)))
Note: Notice the resemblance to the SOLID entity. The only difference being,
the TRACE requires FOUR corners to define itself.
XLine
- 95 -
Typical DXF Group Codes for an XLine Entity:
To list an XLine entity in AutoCAD you type LIST<enter> and select the XLine. To do this in AutoLisp you would:
(setq en(car (entsel "\n Select an XLINE:")))

Would return:
((-1 . <Entity name: 40222960>) (0 . "XLINE") (330 . <Entity

name: 40073cf8>) (5 . "92C") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 .
"0") (100 . "AcDbXline") (10 5181.72 4894.2 0.0) (11 0.983723 0.179691 0.0))
(-1 . <Entity name: 40222960>) -1 - Entity Name (AutoCAD Automatically takes care of this)
(0 . "XLINE") 0 - Entity Type
(5 . "92C") 5 - Handle Name (If handles are turned on)
(8 . "0") 8 - Layer Name
(10 5181.72 4894.2 0.0) 10 - First Point (In WCS)
(11 0.983723 0.179691 0.0) 11 - Unit Direction Vector (In WCS)

(100 ."AcDbXline") 100 - Don't worry about this Subclass marker
Note: There's not much you can do with an XLine so, let's let it go at that. Get on away from here Miss Daisy!
End of Entity DXF Group Code Descriptions
- 96 -
The AutoLisp Tutorial - Extreme
Well you made it. You've read the Beginners, Intermediate, and Expert's tutorials and now you want to apply your
knowledge in real world situations. I believe the best way to approach this is to read through commented code and follow
what is going on. It would be even better if you had the programmers thoughts before starting the program. So, we will do
that. But what code? This I will leave up to you. If you have read all of the tutorials and still can't get the code to do what
you want, click <here> to suggest a program for the Extreme section. I'll start it with a couple of problems I've encountered in
the last year or so. Placing vertices along a polyline bulge and figuring the angle of an arc. I know, seems simple. But what
happens when your start angle is around 350 degrees and your end angle is around 30 degrees. You can't subtract the end
angle from the start angle can you?
Placing vertices along a

Figuring the Angle of an Arc
PolyLine Bulge
PolyLine Bulge
Have you ever tried to recreate a polyline by drawing lines from vertex to vertex only to find out it doesn't work if you have a
polyline bulge? (ARC) Aggravating isn't it. Well, I've found a method to insert vertex points along the polyline bulge area to
recreate a bulge effect and get you closer to what you need. I'm looking for this code....
Arc Angle
Have you ever tried to figure the angle of an arc only to be fustrated by the fact the angle cannot be simply subtracted? It's
true because an arc's angle is always measured counter clock-wise so you could have a starting angle of 350 degrees and an
ending angle of 30 degrees. Can't subtract the end angle from the start angle can you? When it crosses zero, there are
problems. (Angle could also be set to clock-wise instead of counter clock-wise)
The first method I used was to begin at the starting angle and increment the angle by one until I reached the end angle or I
crossed the zero angle. This works but it is a little goofy.
The second method I've seen (sent to me by a visitor) was to reset the UCS to the center point with an angle that matched the
starting angle. Then simply get the ending angle. Not bad. Not bad at all.
The shortest method I've found was to use the built in geometry calculator:
- 97 -
The calculator function we will use is called ANG. The syntax is ANG(apex, endPt1, endPt2). In the illustration above the
apex is P1, the first point is P2, and the third point is P3. You can also do this on the command line. Type CAL and press
enter. Then type ang(cur,cur,cur) and press enter. Now pick the three points.
To do this in autolisp.....you first need to make sure the calculator is loaded:
(if (not c:cal)(arxload "geomcal"))
Then send your points to the calculator:
(setq myAng (cal "ang(p1,p2,p3)")
This should set variable myAng to 51.9180
The AutoLisp Tutorial - DCL

Dialog Control Language
- 98 -
Contents
• Getting Started
• Rows and Columns
• Controls
• Image
• Action
• Set_Tile and Mode_Tile
• List and how to handle them.
• Saving data from the dialog box
• Part 1 - Buttons
• Part 2 - Edit_Box
• Part 3 - List_Box
• Part 4 - PopUp_List
• Part 5 - Radio_Buttons
• Part 6 - Text and Toggle
• Part 7 - Putting it all together
Getting Started
I'm not going to explain everything there is to know about Dialog Control Language. There are plenty of books on the
subject. I will attempt to give you a good understanding of how DCL interacts with AutoLisp. You should be able to write
your first DCL driven Autolisp program in no time. Let's get to it.
Here is the basic order for things to happen inside the AutoLisp file:
(defun C:MyProgram() ; Define the main program
- 99 -
(defun myFunction1() ; Define the functions you need like saveVars
;do stuff here
(defun myFunction2()
;do stuff here
(setq list1(list "a" "b" "c" "d")) ; Build the list if any are required
(setq list2(list "1" "2" "3" "4"))
(setq list3(list "x" "y" "z"))
load_dialog ;Load the DCL file
new_dialog ;Load the DCL definition
start_list ;Put the list in the dialog box

add_list
end_list
start_list ;As many list as you need

add_list
end_list
set_tile ; Set the tiles (if necessary)
mode_tile ; Enable or disable tiles (as necessary)
;Set up as many action tiles as you need.
(action_tile "accept" "(setq d 2)(myFunction1)(done_dialog)")

(action_tile "cancel" "(setq d 1)(myFunction2)(done_dialog)")
;Two action tiles need to have the done_dialog call. One of these needs to save the settings before
; the done_dialog call.
start_dialog ; Start the dialog box
- 100 -
unload_dialog ; Unload the dialog box
; Do stuff if the user presses the cancel key
(if (= d 1)
;do stuff here if cancel was pressed
; Do stuff if the user presses the accept key
(if (= d 2)
;do stuff here if okay was pressed
) ; close the program
We will discuss this in detail later on.
I've found the hardest thing to get a grip on is laying out the dialog box. Please take a look at the rows and columns section
if you need help with laying out a dialog box. For now let's look at the basics. I'm going to throw a lot at you, but don't panic.
I'll cover them a little closer later on. We will cover these items first: button, row, column, boxed_row, and boxed_column.
Okay and Cancel Buttons - The DCL code for a these buttons look like this:
: button { \\ Define the button

key = "accept"; \\ Define the action key (This is my name assigned to this button)
label = " Okay "; \\ This is the text displayed on the button.
is_default = true; \\ Allows the button to activate when the user presses the enter key.
} \\ Close the button definition
: button { \\ Define another button

key = "cancel"; \\ Define the action key. (I chose this name for the button.)
label = " Cancel "; \\ Text displayed on the button.
is_default = false; \\ Does not allow this key to activate when the enter key is pressed.
is_cancel = true; \\ Activate this key when the close button [ X ] is selected.
} \\ Close the button definition
Rows and Columns designate areas to lay your controls on. [Controls are list boxes, edit boxes, buttons, etc. ].
Here is the DCL code for a column:
: column {
- 101 -
}
Here is the DCL code for a row:
: row {
Simple right?
Here is the code for a column with two buttons:
: column {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false; Notice the buttons are stacked on top of each other.
is_cancel = true;
}
Here is the code for a row with two buttons:
: row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
Notice the buttons are side by side.
is_default = false;
is_cancel = true;
}
Let's turn the above into Boxed Rows and Boxed Columns. Here is the code for a boxed_column with two buttons:
- 102 -
: boxed_column {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
Notice the box around the buttons.
is_cancel = true;
}
Here is the code for a boxed_row with two buttons:
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false; Notice the box around the buttons.
is_cancel = true;
}
Now we know the difference between a row and a boxed_row. We also know that controls inside a column get stacked on
top of each other [ vertical ] and controls inside a row are next to each other [ horizontal ].
Important: You should never ever attempt to build a dialog box without a cancel button. Trust me. Or you can do what I
did and find out for yourself.
Overview
Let's take a look at the entire code for the dialog box above, including the LSP file:
DCL FILE NAMED: DCL_TEST.DCL AUTOLISP PROGRAM NAMED: DCL_TEST.lsp
- 103 -
DCL_TEST : dialog {
: boxed_row {
: button {
key = "accept"; (defun C:DCL_TEST()
label = " Okay "; (setq dcl_id (load_dialog "DCL_TEST.dcl"))
(if (not (new_dialog "DCL_TEST" dcl_id) ) (exit))
is_default = true; (action_tile "cancel" "(setq ddiag 1)(done_dialog)")
} (action_tile "accept" "(setq ddiag 2)(done_dialog)")
(start_dialog)
(unload_dialog dcl_id)
(if (= ddiag 1)
: button { (princ "\n \n ...DCL_TEST Cancelled. \n ")
key = "cancel"; )
(if (= ddiag 2)
label = " Cancel "; (alert "You pressed the OKAY button!")
is_default = false; )
)
is_cancel = true;
}
AutoLISP
Let's take a look at the AutoLisp part of this simple program.
First we defined our program:
(defun C:DCL_TEST()
The second thing was to load the DCL file from disk. Insert a path if necessary, but I always liked to use the autocad search
path to find the file. Notice the dcl_id variable used. We will need this later on. This identifies the file opened.
;;;--- Put up the dialog box

(setq dcl_id (load_dialog "DCL_TEST.dcl"))
Since a DCL file can contain multiple dialog box definitions, [ I'll show you an example later on. ] we need to specify which
dialog box we want to load. This is taken care of in the next statement. Notice the name matches the definition inside the
DCL file.
;;;--- See if it is already loaded

(if (not (new_dialog "DCL_TEST" dcl_id) ) (exit))
Next, we define our action keys. These tell the program what to do whenever a user presses a button,
selects an item in a list, etc. Notice the two action keys. "cancel" and "accept" . These match the
keys in the DCL file. I made these names up. You can name them whatever you want as long as it is not
a name used by AutoCAD and it only appears once in each DCL definition. You can't have two controls
- 104 -
with the same key, the program would get confused. So would I!!! Whenever the user presses the
cancel key, the program sets variable ddiag to 1 and closes the dialog box. Upon pressing the Okay
button, [ key = accept ], the program sets variable ddiag to 2 and closes the dialog box. That's it.
Nothing else to add except, you could have just about anything in here, including instructions to
execute a function [ I'll demonstrate that later. ]
;;;--- If an action event occurs, do this function

(action_tile "cancel" "(setq ddiag 1)(done_dialog)")
(action_tile "accept" "(setq ddiag 2)(done_dialog)")
Finally, the big step. Everything is defined, let's display the dialog box.
;;;--- Display the dialog box

(start_dialog)
The program halts here until the dialog box is issued a "done_dialog" call. In the mean time the
user is interacting with the action keys. When the user presses a button the program kills the dialog
box with the unload_dialog call. Notice the dcl_id passed as a parameter. You could have more than
one dialog file open at one time. So, the unload_dialog function needs to know which one to unload.

Finally the dialog box is gone. What next? Find out which button the user pressed? Exactly!
Remember setting the ddiag variable to either 1 or 2. We will use that now to determine which button
was pressed. There is a better way to do this, I'll show you later.
;;;--- If the cancel button was pressed - display message

(if (= ddiag 1)
(princ "\n \n ...DCL_LSP Cancelled. \n ")
)
;;;--- If the "Create" button was pressed

(if (= ddiag 2)
(alert "You pressed the OKAY button!")
)
And the last step, close the autolisp program.
The basic DCL model

I will now give you the model I use for 98% of all dialog based programs I write. I start with this basic program and build
from there. It is basically the same thing we've gone over before. I put up a dialog box. I allow the user to press buttons and
manipulate data. The only difference is, when the user presses the OKAY button I save the settings in the dialog file before it
closes. I do this inside the action key call with a function called saveVars. Without further ado, here's the model:
- 105 -
The DCL File:
EXAMPLE : dialog {
label = "EXAMPLE.lsp"; \\ Puts a label on the dialog box
initial_focus = "textval"; \\ Sets the initial focus
: column {
: row {
: boxed_column {
: edit_box { \\ The edit_box control - Something new!
key = "textval";
label = "Text Value to Find";
edit_width = 30;
value = "";
}
}
}
: row {
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
}
}
The AutoLisp File:
;;;--- EXAMPLE.lsp - Text Find
(defun saveVars()
;;;--- Save the input from the dialog box
(setq textVal (get_tile "textval"))
)
(defun C:EXAMPLE()
;;;--- Load the dcl file

(setq dcl_id (load_dialog "EXAMPLE.dcl"))
;;;--- Load the dialog definition if it is not already loaded

(if (not (new_dialog "EXAMPLE" dcl_id) ) (exit))

(action_tile "accept" "(setq ddiag 2)(saveVars)(done_dialog)")
- 106 -
(start_dialog)

(if (= ddiag 1)
(princ "\n \n ...EXAMPLE Cancelled. \n ")
)
;;;--- If the "Okay" button was pressed

(if (= ddiag 2)
(princ "\n \n ...Example Complete!")
)
;;;--- Suppress the last echo for a clean exit

(princ)
Screen Shot:
If you could not follow some of the autolisp functions, you can ignore them for now or read the Autolisp Tutorial.
This is the model. Very little will change from this setup. You may add some controls to the DCL file which in turn will add
Action calls and influence the number of lines inside the saveVars routine. The only other thing that will change is inside the
OKAY button function. [ When ddiag = 2 ]. You will have to tell the program what to do when all of the information is
gathered. We will cover these later.
Rows and Columns
Let's get a feel for laying out a dialog box using nested rows and columns. I'll do this by showing you the DCL code next to
a picture of the dialog box. I can't think of any easier way to do it. Ignore all of the Labels and TEXT controls. I will use
these to visually show the location of things.
- 107 -
Example 1:
EXAMPLE : dialog {
label = "EXAMPLE.lsp";
: column {
: boxed_column {
label = "column 1";
: boxed_column {
label = "column2";
}
: boxed_column {
label = "column 3"; Column
} Column
} Column<\p>
ok_cancel;
}
}
EXAMPLE : dialog {
: column {
: boxed_row {
label = "row 1";
: boxed_column {
label = "column2";
}
: boxed_column {
label = "column 3"; Notice I changed the first boxed column into a boxed row.
}
} Row
ok_cancel; Column
} Column
}
- 108 -
EXAMPLE : dialog {
: column {
: boxed_column {
label = "column 1";
: boxed_column {
label = "column2"; : text
{
key = "t1";
value = "Text1";
}
: text {
key = "t2";
value = "Text2";
}
}
: boxed_column {
label = "column 3"; :
text {
key = "t3";
value = "Text3";
} Column
: text { Column
key = "t4"; Column<\p>
value = "Text4";
}
}
}
ok_cancel;
}
}
- 109 -
EXAMPLE : dialog {
: column {
: boxed_row {
label = "row 1";
: boxed_column {
label = "column2"; : text
{
key = "t1";
value = "Text1";
}
: text {
key = "t2";
value = "Text2";
}
}
: boxed_column {
label = "column 3"; :
text {
key = "t3"; Row
value = "Text3"; Column
} Column
: text {
key = "t4";
value = "Text4";
}
}
}
ok_cancel;
}
}
- 110 -
EXAMPLE : dialog {
: column {
: boxed_row {
label = "row 1";
: boxed_row {
label = "row 2";
: text {
key = "t1";
value = "Text1";
}
: text {
key = "t2";
value = "Text2";
}
}
: boxed_row {
label = "row 3"; :
text {
Row
key = "t3";
Row
value = "Text3";
} Row
: text {
key = "t4";
value = "Text4";
}
}
}
ok_cancel;
}
}
- 111 -
EXAMPLE : dialog {
: column {
: boxed_column {
label = "row 1";
: boxed_row {
label = "row 2";
: text {
key = "t1";
value = "Text1";
}
: text {
key = "t2";
value = "Text2";
}
}
: boxed_row {
label = "row 3"; :
text {
key = "t3";
value = "Text3"; Column
} Row
: text { Row
key = "t4";
value = "Text4";
}
}
}
ok_cancel;
}
}
I hope this puts an end to the rows and columns issue. If not, you know where to find me.
CONTROLS
Let's take a look at the different controls you can put on the dialog box. You've seen a few of them in the overview portion but
let's go over the majority of them now. I will only show the most used properties for each control.
- 112 -
LAYOUT CONTROLS:
: column { Column
label = "My Column";
} You can omit the label.
: boxed_column { Boxed Column

label = "My Column";
: row { Row
label = "My Row";
: boxed_row { Boxed Row

label = "My Row";
: spacer { A normal spacer to help align other controls. You can omit the width and
width = 10; height properties.
height = 15;
}
: spacer_0; A spacer that usually has no width. It simply means, if you have to stretch
something in this row to make things fit, stretch this spacer instead of the other
items..
: spacer_1; The smallest spacer that's visually noticable.
BUTTON
key = The name you assign to the button.
: button { label = The text displayed on the button.

key = "button1;
label = "Okay"; is_cancel = Determines if this is the cancel button. One
is_tab_stop = true; control must be assigned to be the cancel action.
is_cancel = false;
is_default = true; is_default = Determines if this button activates when the
width = 15; user presses the enter key.
height = 10;
mnemonic = "B"; mnemonic = Determines if you can press ALT+B to move
} to this action key. You assign the letter and DCL will
underscore the letter on the dialog box to let the user know
it is ALT-able. If that is a word!
- 113 -
BOXED RADIO COLUMN, RADIO COLUMN, & RADIO BUTTON
: radio_column { // Use boxed_radio_column if a box is required.

label = "Choices"; // Label for the column or boxed_column
key = "choices"; // Action key for the radio column
: radio_button {
// First radio button
label = "Choice 1";
key = "choice1";
}
: radio_button {
// Second radio button
label = "Choice 2";
key = "choice2";
}
: radio_button {
// Third radio button
label = "Choice 3";
key = "choice3";
}
: radio_button {
// Fourth radio button
label = "Choice 4";
key = "choice4";
}
} // Close the radio_column
BOXED RADIO ROW, RADIO ROW, & RADIO BUTTON
: radio_row { // Use boxed_radio_row for box.

label = "Choices"; // Label for the row or boxed_row
key = "choices"; // Action key for the radio row
: radio_button {
// First radio button
label = "1";
key = "choice1";
}
: radio_button {
// Second radio button
label = "2";
key = "choice2";
}
: radio_button {
// Third radio button
label = "3";
key = "choice3";
}
: radio_button {
// Fourth radio button
label = "4";
key = "choice4";
}
} // Close the radio_row
- 114 -
EDIT BOX
: edit_box {
key = "myval"; // Action key
label = "Value:"; // Label for the edit box
edit_width = 10; // Character width
value = ""; // Initial value
}
LIST BOX
: list_box {
label ="Choose Items"; // Label for the list box
key = "mylist"; // Action key
height = 15; // Height of list box
width = 25; // Width of list box
multiple_select = true; // Multiple Select = TRUE
fixed_width_font = true; // Use fixed with font = TRUE
value = "0"; // Initial selection = 1st item
} Fixed Width Font = TRUE
Multiple Select = TRUE

View of list box with... View of list box with...
Fixed Width Font = FALSE. Fixed Width Font = FALSE.
Multiple Select = TRUE. Multiple Select = FALSE.
POPUP LIST
: popup_list {
key = "mylist"; // Action key
label = "Select Item"; // Label
fixed_width_font = false; // Use fixed with font = false
width = 15; // Width of list box
value = 0; // Initial selection = 1st item
}
- 115 -
TEXT
: text {
key = "mytext"; // Action key
value = "This is text!"; // Value
}
Okay. That's it for controls. There are others but, these are the most used controls. Let's move on
Image
Image
An Image is used to display a vector graphic picture inside a rectangle. To create the image you can use three different
methods.
• Vector_image - Draws a single straight line in the current image.

• Fill_image - Draws a filled rectangle in the current image.
• Slide_image - Draws an AutoCAD slide in the image.
For this tutorial we will concentrate on the Slide_Image function. Everyone knows how to create a slide right? The MSLIDE
command. Okay. We will assume our image is ready.
Let's look at the DCL Image definition and the AutoLisp functions required to display the image.
DCL - You must supply either the width and height or one of these plus an aspect_ratio.
: image {
key = "sld";
height = 30;
width = 30;
color = 0;
is_enabled = false;
is_tab_stop = false;
}
AutoLisp
;;;--- First we need a slide name

(setq mySlideName "c:/acad/myslide.sld")
;;;--- Second we need the key to the image control

(setq myKey "sld")
;;;--- Next we send the slide name and the key to the update function
(upDateImage mySlideName myKey)
- 116 -
; NOTE: Notice mySlideName becomes sldName and myKey becomes key when passed
; as parameters to the upDateImage function.
;;;--- Function to update the slide
(defun upDateImage(sldName key)
;;;--- Get the width of the slide

(setq width (dimx_tile key))
;;;--- Get the height of the slide

(setq height (dimy_tile key))
;;;--- Start the slide definition

(start_image key)
;;;--- Wipe out the background

(fill_image 0 0 width height 0)
;;;--- Put the slide in the image area

(slide_image 0 0 width height sldName)
;;;--- Finish the slide definition

(end_image)
This function can be used over and over to display any slide image in an image control. Use the upDateImage function after
the new_dialog call and before the action_tile statements. You can also use this function while the dialog box is displayed in
one of your action calls. We will use this later on in the tutorial so you can see it in action.
Action
In order for the dialog box to respond to user interaction, you must set up an action event. A trigger, to fire when the user
selects an item from a list or presses a button. This works off of the KEY defined for each control inside the DCL file. If the
key for a button is named "mybutton" then you must have an action named "mybutton". Otherwise the user will press the
button and nothing will happen. Let's take a look at the action_tile.
(action_tile "key" "action")
The action_tile has two parameters. "Key" and "action".
"Key" - The name of the key you defined with the control inside the DCL file.
- 117 -
"Action"- The action you want taken when the action event is fired. You can set a variable or run a function.
Examples:
Let's take for example, you have a button named "test" and you want to set the variable named myTEST to 1 if the user
presses the button:
(action_tile "test" "(setq myTest 1)")
Notice the key is in quotes and the setq function is in quotes. This is standard procedure for the action_tile statement. Next
let's say you have the same thing except you want to run a function named "saveVars" when the user presses the test button.
(action_tile "test" "(saveVars)")
Notice is is the same as the above. The (saveVars) is inside quotes.
What if you wanted to do both, run the function and set a variable?
(action_tile "test" "(setq myTest 1)(saveVars)")
Simply put both inside the quotes.
One more thing....What if the button is set to be the cancel or accept button for the dialog box? No problem...
(action_tile "test" "(setq myTest 1)(saveVars)(done_dialog)")
Add the done_dialog statement to the end. [ Inside the quotes ]
That is about all there is to an action_tile. Remember, anything with a key can have an action call.
Set_Tile and Mode_Tile
Set_Tile - is used to set the value of a control.
(set_tile "key" "value")
Set_Tile has two parameters. "Key" and "Value".
"Value"- The new value for the control.
• Edit_box
o (set_tile "mybox" "Jeff") Displays Jeff in the edit box.
o (set_tile "mybox" "4'-3 1/2") Displays 4'-3 1/2 in the edit box.
- 118 -
• List_box
o (set_tile "mylist" "0") Selects the first item in the list.
o (set_tile "mylist" "5") Selects the sixth item in the list.
o (set_tile "mylist" "") No Items are selected.
• PopUp_List
o (set_tile "mylist" "0") Selects the first item in the list.
o (set_tile "mylist" "5") Selects the sixth item in the list.
o (set_tile "mylist" "") No Items are selected.
• Toggle
o (set_tile "mytog" "0") Removes the check from the box.
o (set_tile "mytog" "1") Checks the box.
• Radio_Button
o (set_tile "myradio1" "1") Moves the selection to the first radio button.
o (set_tile "myradio2" "1") Moves the selection to the 2nd radio button.
Use Set_Tile after the new_dialog and before the action_tiles. Set_Tile can also be used as a function while the dialog box is
displayed.
Mode_Tile - is used to enable or disable a control.
(mode_tile "key" value)
Mode_Tile has two parameters. "Key" and Value.
Value- The new value for the control. 0 = Enabled 1 = Disabled
(mode_tile "mylist" 0) Enables the list box
(mode_tile "mylist" 1) Disables the list box
Use Mode_Tile after the new_dialog call and before the action_tiles. Mode_Tile can also be used as a function while the
dialog box is displayed.
That is all there is to set_tile and mode_tile. We will used them later on in the tutorial so you can see them in action.
List and how to handle them.
List_box and popup_list handle a list of items in basically the same manner. You have to load your list into the list box and
at some point you have to decide which item or items were selected. In the "Saving data from a dialog box" I cover how to
find the selected items from a list_box and a popup_list. How do we get the list inside the list_box? That is what we need to
cover in this section. So let's get started.
- 119 -
If you looked at the previous sections you know the AutoLisp and DCL basic model. Let's get a copy of that in this section
so we can look at it. I will replace the edit_box with a list_box control and add the code to handle the list. The list handling
code is shown in the "Saving data from a dialog box" section of this tutorial.
I will show the revised and new code in red below. All of the black code is unchanged from the Basic Model and the
instructions from the "list_box multiple selection" area of the "Saving data from a Dialog box" page.
The Basic Revised Model

The DCL File:
EXAMPLE : dialog {
label = "EXAMPLE.lsp"; \\ Puts a label on the dialog box
: column {
: row {
: boxed_column {
: list_box { \\ I replaced the edit_box with a list_box.
label ="Choose Items";
key = "mylist";
height = 15;
width = 25;
multiple_select = true; \\ Multiple selection is on
fixed_width_font = true; \\ Fixed Width Font is on
value = "0";
}
}
}
: row {
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
}
}
The AutoLisp File:
;;;--- EXAMPLE.lsp
;;;--- I replaced the saveVars routine with the one from the "Save data from a list" section of this tutorial.
;;; I also changed the things marked in red.
- 120 -
(defun saveVars(/ readlist count item)
;;;--- Notice the "mylist" is the action key associated with the DCL file and
;;; the myList is the variable for the list built below.
;;;--- Setup a list to hold the selected items

(setq retList(list))
;;;--- Save the list setting

(setq readlist(get_tile "mylist"))
;;;--- Setup a variable to run through the list

(setq count 1)
;;;--- cycle through the list getting all of the selected items
(while (setq item (read readlist))
(setq retlist(append retList (list (nth item myList))))
(while
(and
(/= " " (substr readlist count 1))
(/= "" (substr readlist count 1))
)
(setq count (1+ count))
)
(setq readlist (substr readlist count))
)
)
(defun C:EXAMPLE()
;;;--- I need to build a list of data

(setq myList(list "1" "2" "3" "4" "5" "6" "7" "8"))

(setq dcl_id (load_dialog "EXAMPLE.dcl"))

(if (not (new_dialog "EXAMPLE" dcl_id) ) (exit))
;;;--- Here, I add the data to the list_box control

;;; I do this after the new_dialog call and before the action_tiles.
(start_list "mylist" 3)
(mapcar 'add_list myList)
(end_list)
;;;--- Notice the "mylist" is the action key associated with the DCL file and
;;; the myList is the variable for the list built above.



(start_dialog)
- 121 -
(if (= ddiag 1)
(princ "\n \n ...EXAMPLE Cancelled. \n ")
)

(if (= ddiag 2)
;;;--- Here, I decide what to do with my data

;;; I'm going to print each selected item on the command line.
(foreach a retList
(princ "\n")(princ a)
)

(princ)
So, in order to display a list in a dialog box, you must first build the list. Then use the start_list, add_list, and end_list
functions just after the new_dialog call and before the action_tiles. This is the same for both a list_box and a popup_list. That
wasn't so bad. Was it?
Saving data from a dialog box "
In this section we are going to take a look at the SaveVars routine and disect it for each type of control. The types of controls
that we sometimes need to save are :
Edit_box - List_box - Popup_List - Radio_Buttons - Radio_Column - Radio_Row - Toggle
The SaveVars routine is executed just before the dialog box is issued a done_dialog call. You cannot get the data from the
dialog box once it has been shut down. If you remember our action calls in the AutoLisp Program, they looked something like
this:

(action_tile "accept" "(saveVars)(done_dialog)")
Notice the (saveVars) is just before the (done_dialog). This is the proper order. The settings from
the dialog box will be saved just before it is shut down.
The SaveVars routine always has the same definition:
(defun saveVars()
;stuff here
That's the shell. We need to work on the "stuffing". Let's get to it.
Stuffing
There are three parts to a control with an action call back statement.
- 122 -
1. The DCL definition
2. The action call in the AutoLisp file.
3. The code inside the SaveVars routine.
In each of the following controls I will show you all three parts so we know how to put it all
together later. Although, all of the parts are important, try to focus on the SaveVars routine.
Edit_box - List_Box_Single_Selection - List_Box_Multiple_Selection - Popup_List
Radio_Column - Radio_Row - Toggle - Ok_Cancel
Edit_Box
: edit_box {
key = "edbox";
label = "Bolt Circle Diameter:";
1 edit_width = 8;
value = "10";
}
No Action call required. We will get the data the user typed when we use the SaveVars routine. But, if your deadset
about doing something when the user types in the edit box, here you go:
2
(action_tile "edbox" "(doThisFunction)")
To get the data as a real number: To get the data as a string:
(defun saveVars() (defun saveVars()

3
(setq edBox(distof(get_tile "edbox"))) (setq edBox(get_tile "edbox"))
) )
NOTE: Notice I used the key name as the variable to store the data in. You will find this method makes it easier to
keep things straight. DCL is case sensitive so, I never capitalize key names, only autolisp variable names if they are
made up of more than one word. Like: thisIsMyVariable.
List_Box Single Choice Only
1 : list_box {
key = "mylist";
label = "Available Choices";
multiple_select = "FALSE"; // Sets single selection
width = 40;
- 123 -
height = 20;
fixed_width_font = true; // Equally spaced characters
value = ""; // Start with no item selected
}
No Action call required. We will get the selected item when we use the SaveVars routine. But, sometimes you need
to change things in the dialog box if the user makes a selection, so:
2
(action_tile "edbox" "(doThisFunction)")
(defun saveVars()
;;;--- Get the selected item from the list

(setq sStr(get_tile "mylist"))
;;;--- If the index of the selected item is not "" then something was selected
(if(/= sStr "")
(progn
;;;--- Something is selected, so convert from string to integer

(setq sIndex(atoi sStr))
;;;--- And get the selected item from the list

(setq sName(nth sIndex myList))
)
;;;--- Else, nothing is selected

(progn
3
;;;--- Set the index number to -1
(setq sIndex -1)
;;;--- And set the name of the selected item to nil

(setq sName nil)
)
)
)
Notes:
1. This should only be used when single selection is required. This will not work on multiple selection.
2. This is assuming there is a list of items called myList.
List_Box Multiple Choice
: list_box {
key = "mylist";
label = "Available Choices";
multiple_select = "TRUE"; // Sets multiple selection
1 width = 40;
height = 20;
fixed_width_font = false; // Use default font [ no alignment ]
value = "4"; // Start with item 5 selected.
}
2 No Action call required. We will get the selected items when we use the SaveVars routine. But, sometimes you need
- 124 -
(action_tile "mylist" "(doThisFunction)")


(setq readlist(get_tile "files"))

(setq count 1)
3 (setq retlist(append retList (list (nth item fileNames))))
(while
(and
)
)
)
)
Note: This method can be used for a single or multiple selection list_box.
PopUp_List
: popup_list {
key = "mylist"; // action key
fixed_width_font = false; // fixed width font off
1
width = 20; // width of popup list
height = 20; // height of popup list
}
2
(action_tile "mylist" "(doThisFunction)")
(defun saveVars()
;;;--- Get the selected item from the list

(setq sStr(get_tile "mylist"))
3
(if(= sStr "")(alert "No Item was Selected!"))
Radio_Column and Radio_Buttons
1 : radio_column { // Use boxed_radio_column if a box is required.

label = "Choices"; // Label for the column or boxed_column
key = "choices"; // Action key for the radio column
- 125 -
: radio_button { // First radio button
label = "Choice 1";
key = "choice1";
}
: radio_button { // Second radio button

label = "Choice 2";
key = "choice2";
}
: radio_button { // Third radio button

label = "Choice 3";
key = "choice3";
}
: radio_button { // Fourth radio button

label = "Choice 4";
key = "choice4";
}
} // Close the radio_column

No Action call required. We will get the selected item when we use the SaveVars routine. But, sometimes you need to
change things in the dialog box if the user makes a selection, so:
(action_tile "choices" "(doThisFunction)") // If any choice is made

2
(action_tile "choice1" "(doThatFunction)") // If choice1 is made
(action_tile "choice2" "(doDisFunction)") // If choice2 is made
etc.
(defun saveVars()
;;;--- Get the key of the choice made

;;; [ returns "choice1" "choice2" "choice3" or "choice4" ]
(setq choicesVal(get_tile "choices"))
)
3
OR
(defun saveVars()
;;;--- Get the value of each item

(setq choice1(atoi(get_tile "choice1"))) // 0 = not chosen 1 = chosen
- 126 -
Radio_Row And Radio_Buttons
: radio_row { // Use boxed_radio_row if a box is required.

label = "Choices"; // Label for the row or boxed_row
key = "choices"; // Action key for the radio row
: radio_button { // First radio button

label = "Choice 1";
key = "choice1";
}
: radio_button { // Second radio button

label = "Choice 2";
key = "choice2";
1 }
: radio_button { // Third radio button

label = "Choice 3";
key = "choice3";
}
: radio_button { // Fourth radio button

label = "Choice 4";
key = "choice4";
}
} // Close the radio_row

(action_tile "choices" "(doThisFunction)") // If any choice is made

2
(action_tile "choice1" "(doThatFunction)") // If choice1 is made
(action_tile "choice2" "(doDisFunction)") // If choice2 is made
etc.
3 (defun saveVars()

;;; [ returns "choice1" "choice2" "choice3" or "choice4" ]
(setq choicesVal(get_tile "choices"))
OR
(defun saveVars()

- 127 -
Toggle
: toggle {
key = "tog1"; // Action key
1
label = "Name"; // Label
}
No Action call required. We will get the value of the toggle when we use the SaveVars routine. But, sometimes you
need to change things in the dialog box if the user makes a selection, so:
2
(action_tile "tog1" "(doThisFunction)")
(defun saveVars()
;;;--- Get the selected item from the radio column

3 (setq tog1Val(atoi(get_tile "tog1"))) // 0 = unchecked 1 = checked
Ok_Cancel
ok_cancel; // Only one line required

1
Note: I usually define my own okay and cancel buttons using two standard buttons, but this works fine.
You will need two action calls for this button...both close the dialog box but the accept or "Okay" key will save the dialog
box settings before shutting the dialog box down.

2
Ahh....finally the SaveVars routine shows up.

3 Nothing to do in the saveVars routine for these buttons.
Part 1 - Buttons
Let's build a working DCL file showing us exactly how to handle buttons.
- 128 -
We will build a DCL file containing three buttons plus a Close [ Cancel ] button. Each of the three buttons will display a
message when pressed.
Layout thoughts: I will place the buttons in a column, (stacked on top of each other). Then I'll put the Close button at the
bottom on a row of it's own. So...I'll need something like this:
: column {
: boxed_column {
: button {
// Put code for button 1 here
}
: button { ]
}
: button { ]
}
}
: boxed_row {
: button {
// Put code for the Close button here
}
}
}
Let's copy in the code for the header and all of the controls above. I'll show them in red. Notice the key names and labels had
to be changed.
SAMPLE1 : dialog {
label = "Sample Dialog Box Routine - Part 1";
: column {
: boxed_column {
: button {
key = "but1";
label = "Button 1";
is_default = false;
}
: button {
key = "but2";
label = "Button 2";
is_default = false;
}
: button {
key = "but3";
label = "Button 3";
is_default = false;
}
}
: boxed_row {
: button {
key = "cancel";
label = "Close";
- 129 -
is_default = true;
is_cancel = true;
}
}
}
Right click and copy the above. Open NotePad and paste it. Save the file as SAMPLE1.DCL Be sure to change the
"Save as Type" drop down box to "All Files" before saving it or it will put a ".txt" extension on the file name. Save this
file somewhere in the AutoCAD search path.
Next we will get a copy of the AutoLisp model and revise it. All new code is shown in red.
(defun C:SAMPLE1()

(setq dcl_id (load_dialog "SAMPLE1.dcl"))

(if (not (new_dialog "SAMPLE1" dcl_id))
(progn
(alert "The SAMPLE1.DCL file could not be loaded!")
(exit)
)
)

(action_tile "cancel" "(done_dialog)")

(start_dialog)
;;;--- Unload the dialog box


(princ)
I removed several lines from the model. I took out the part that checked to see if we hit the Cancel or Okay buttons. We
don't need either in this program. I also removed the action tile for the okay button and removed "(setq ddiag 1)" from the
cancel button.
Right click and copy the above. Open NotePad and paste it. Save the file as SAMPLE1.LSP Be sure to change the
Let's load the program and see what the DCL file looks like. On the command line type this:
Command: (load "sample1") and press enter
You should see this
- 130 -
C:Sample1
Command:
Now type Sample1 and press enter. If everything went according to plan you should see this on your screen:
The buttons do not work yet. Except for the close button. It should work fine. We need to add the function to print three
different messages when the user presses each button. Let's send a parameter to the function to decide which message to
display. If the parameter equals 1 we will print the first message. If 2 then print the second message. If 3 print the third
message. Something like this:
(defun doButton(a)
(cond
((= a 1)(alert "Button 1 was pressed!"))
)
)
Now we need to add the action calls for each of the buttons:
(action_tile "but1" "(doButton 1)")

This will send a parameter of 1,2, or 3 to the doButton function depending on which button is pressed.
Let's add the doButton function and the action calls to the autolisp program. It should look like this:
(defun doButton(a)
(cond
)
)
(defun C:SAMPLE1()

- 131 -
(progn
(exit)
)
)


(start_dialog)


(princ)
Save it and test it out. Everything working okay?
When you get your program tested and everything is working, move the blue line above, [ (defun C:SAMPLE1() ] all the way
to the top of the file. This will make all of your variables local and will reset them all to nil when the program ends.
That's it. We're done.
Part 2 - Edit_Box
Let's build a working DCL file showing us exactly how to handle edit boxes.
We will build a DCL file containing two edit boxes plus a Okay and Cancel button. The information in the two edit boxes
will be displayed after selecting the Okay button.
- 132 -
Layout thoughts: I will place the edit boxes in a column, (stacked on top of each other). Then I'll put the Okay and Cancel
buttons at the bottom in a row. So...I'll need something like this:
: column {
: boxed_column {
: edit_box {
// Put code for edit_box 1 here
}
: edit_box {
// Put code for edit_box 3 here
}
}
: boxed_row {
: button {
// Put code for the Okay button here
}
: button {
// Put code for the Cancel button here
}
}
}
to be changed.
SAMPLE2 : dialog {
: column {
: boxed_column {
: edit_box {
key = "username";
label = "Enter your Name:";
edit_width = 15;
value = "";
initial_focus = true;
}
: edit_box {
key = "userage";
label = "Enter your Age:";
edit_width = 15;
value = "";
}
}
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
- 133 -
}
}
}
(defun C:SAMPLE2()


(progn
(exit)
)
)


(start_dialog)

;;;--- If the user pressed the Cancel button

(if(= ddiag 1)
(princ "\n Sample2 cancelled!")
)
;;;--- If the user pressed the Okay button

(if(= ddiag 2)
(progn
(princ "\n The user pressed Okay!")
)
)

(princ)
- 134 -
You should see this
C:Sample2
Command:
Looking good so far. We need to add the SaveVars function to save the strings in the edit boxes when the Okay button is
pressed. Look at the blue text in the Sample2.lsp program above.
The edit box for the name needs to be a string. Dialog boxes return strings, so we do not need to modify it. All we have to
do is use the get_tile function.
(setq userName(get_tile "username"))
The edit box for Age needs to be an integer. We will have to modify the get_tile results by using the ATOI function. This
function converts a string to an integer.
(setq userAge( atoi (get_tile "userage")))
If we needed to convert to an Real number we would use DISTOF function instead of the ATOI function.
Our SaveVars routine would look like this:
(defun saveVars()
(setq userAge( atoi (get_tile "userage")))
)
Our program would now look like this:
(defun saveVars()
(setq userAge(atoi(get_tile "userage")))
)
- 135 -
(defun C:SAMPLE2()


(progn
(exit)
)
)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
Last item. We need to replace the line in the program: (princ "\n The user pressed Okay!") with something to
modify and display the userName and userAge data. Let's do something simple. We will find out how many days old this
person is.

(if(= ddiag 2)
(progn
;;;--- Multiply the users age x 365 to get the number of days.
(setq userAge(* userAge 365))
;;;--- Display the results

(alert (strcat userName " is " (itoa userAge) " days old."))
)
)
Add the above to the file, save it and test it out. Everything working okay?
- 136 -
Part 3 - List_Box
Let's build a working DCL file showing us exactly how to handle list boxes.
We will build a DCL file containing two list boxes plus an Okay and Cancel button. We will set the first list box to single
selection and the second to multiple selection. The selected items will be displayed on the screen after the user presses the
Okay button.
Layout thoughts: I will place the list boxes in a row, (side by side). Then I'll put the Okay and Cancel buttons in a row at
the bottom of the dialog box. So...I'll need something like this:
: column {
: boxed_row {
: list_box {
// Put code for list_box 1 here
}
: list_box {
// Put code for list_box 2 here
}
}
: boxed_row {
: button {
}
: button {
}
}
}
Let's copy in the code for the header and all of the controls above from the "Controls" section of this tutorial. I'll show them in
red. Notice the key names and labels had to be changed.
- 137 -
SAMPLE3 : dialog {
: column {
: boxed_row {
: list_box {
label ="Choose Item";
key = "mylist1";
height = 15;
width = 25;
multiple_select = false;
fixed_width_font = true;
value = "";
}
: list_box {
label ="Choose Items";
key = "mylist2";
height = 15;
width = 25;
multiple_select = true;
value = "";
}
}
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
(defun C:SAMPLE3()


(progn
- 138 -
(exit)
)
)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
You should see this
C:Sample3
Command:
- 139 -
Looks good but, there is nothing to choose. Let's add some data to the list boxes. We will need two list. We will call the list
for the first list box myList1 and the second myList2.
(setq myList1(list "Electrical" "Structural" "Plumbing" "Foundation"))
(setq myList2(list "Plastic" "Steel" "Aluminum" "Concrete"))
Alrighty then, we have our list built. All we have to do is put them in the dialog box. We will use the start_list, add_list, and
end_list functions. Start_list tells DCL which list_box we are going to edit. The identification is made by using the list_box
KEY. The first list has a key of "mylist1" and the second has a key of "mylist2". So the start_list function would look like
this:
(start_list "mylist1" 3) ; The 3 means we want to delete the old contents and start new.
Next we use the add_list function to tell DCL which list to put in the list_box. We use the mapcar function to apply add_list
to each member in the list. Our list for the first list_box is named myList1. So...
(mapcar 'add_list myList1)
Finally we use the end_list function to tell DCL to display the new contents because we are through editing the list.
(end_list)
To look at it all together:
(start_list "mylist1" 3)
(end_list)
(end_list)
- 140 -
Let's add all of this to the AutoLisp program and see what it looks like.
(defun C:SAMPLE3()



(progn
(exit)
)
)
(end_list)
(end_list)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
Notice the location of the red lines. We create the list before loading the dialog box. We add the list to the dialog box after it
is loaded with new_dialog and before the action_tile statements. This is the order you should use.
Looking good so far. We need to add the SaveVars function to save the selected items from the list boxes when the Okay
button is pressed. Look at the blue text in the Sample3.lsp program above.
- 141 -
Let's steal the saveVars routine from the list_box control on the "List and how to handle them" page of this tutorial and
modify it. I'll show the modifications in red.


(setq readlist(get_tile "mylist1"))

(setq count 1)
(setq retlist(append retList (list (nth item myList1))))
(while
(and
)
)
)
)
Wow! That was easy. Wait a minute, we have two list boxes. We will have to create a function out of this or simply copy
this and do it twice. For now, let's just do it twice.



(setq count 1)
(setq retlist(append retList (list (nth item myList1))))
(while
(and
)
)
)

(setq retList2(list))
- 142 -

(setq count 1)
(setq retlist2(append retList2 (list (nth item myList2))))
(while
(and
)
)
)
)
(defun C:SAMPLE3()



(progn
(exit)
)
)
(end_list)
(end_list)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
- 143 -
)
)

(princ)
modify and display the selected items. Let's do something simple. We will tell the user what was selected out of each list..

(if(= ddiag 2)
(progn
;;;--- Inform the user of his selection from the first list
(princ (strcat "\n You chose " (car retList) " from the first list box."))
;;;--- Inform the user of his selections from the second list
(princ "\n Your choice(s) from the second list box :")
(foreach a retList2
(princ "\n ")
(princ a)
)
)
)
- 144 -
Part 4 - PopUp_List
Let's build a working DCL file showing us exactly how to handle popup list.
We will build a DCL file containing two pop_up list plus an Okay and Cancel button. The selected items will be displayed
on the screen after the user presses the Okay button.
Layout thoughts: I will place the popup_list in a row, (side by side). Then I'll put the Okay and Cancel buttons in a row at
the bottom of the dialog box. So...I'll need something like this:
: column {
: boxed_row {
: popup_list {
// Put code for popup_list 1 here
}
: popup_list {
// Put code for popup_list 2 here
}
}
: boxed_row {
: button {
}
: button {
}
}
}
- 145 -
SAMPLE4 : dialog {
: column {
: boxed_row {
: popup_list {
key = "mylist1";
label = "Select Item";
width = 30;
value = "";
}
: popup_list {
key = "mylist2";
label = "Select Item";
width = 30;
value = "";
}
}
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
(defun C:SAMPLE4()


(progn
(exit)
- 146 -
)
)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
You should see this
C:Sample4
Command:
Looks good but, there is nothing to choose. Let's add some data to the popup list boxes. We will need two list. We will call
the list for the first popup list box myList1 and the second myList2.
- 147 -
Alrighty then, we have our list built. All we have to do is put them in the dialog box. We will use the start_list, add_list, and
end_list functions. Start_list tells DCL which popup list box we are going to edit. The identification is made by using the
popup list box KEY. The first popup list box has a key of "mylist1" and the second has a key of "mylist2". So the start_list
function would look like this:
(start_list "mylist1" 3) ; The 3 means we want to delete the old contents and start new.
Next we use the add_list function to tell DCL which list to put in the popup list box. We use the mapcar function to apply
add_list to each member in the list. Our list for the first popup list box is named myList1. So...
Finally we use the end_list function to tell DCL to display the new contents because we are through editing the popup list
box.
(end_list)
To look at it all together:
(end_list)
(end_list)
Let's add all of this to the AutoLisp program and see what it looks like.
(defun C:SAMPLE4()



(progn
(exit)
)
)
(end_list)
(end_list)
- 148 -

(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
Notice the location of the red lines. We create the list before loading the dialog box. We add the list to the dialog box after it
is loaded with new_dialog and before the action_tile statements. This is the order you should use.
Looking good so far. We need to add the SaveVars function to save the selected items from the popup list boxes when the
Okay button is pressed. Look at the blue text in the Sample4.lsp program above.
Let's steal the saveVars routine from the popup list box control on the "Saving data from the dialog box" page of this tutorial
and modify it. I'll show the modifications in red.
(defun saveVars()
;;;--- Get the selected item from the first list

(setq sStr1(get_tile "mylist1"))
;;;--- Make sure something was selected...

(if(= sStr1 "")>
(setq myItem1 nil)
(setq myItem1 (nth (atoi sStr1) myList1))
)
Wow! That was easy. Wait a minute, we have two pop_up list boxes. We will have to create a function out of this or simply
copy this and do it twice. For now, let's just do it twice.
- 149 -
(defun saveVars()
;;;--- Get the selected item from the first list


(if(= sStr1 "")>
(setq myItem1 "Nothing")
)
;;;--- Get the selected item from the second list


(if(= sStr2 "")>
(setq myItem2 "Nothing")
)
)
(defun C:SAMPLE4()



(progn
(exit)
)
)
(end_list)
(end_list)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
- 150 -
)
)

(princ)
modify and display the selected items. Let's do something simple. We will tell the user what was selected out of each popup
list..

(if(= ddiag 2)
(progn
;;;--- Inform the user of his selection from the first list
(princ (strcat "\n You chose " myItem1 " from the first popup list box."))
;;;--- Inform the user of his selections from the second list
(princ (strcat "\n You chose " myItem2 " from the second popup list box."))
)
)
- 151 -
Part 5 - Radio Buttons
Let's build a working DCL file showing us exactly how to handle radio buttons.
The first thing you need to know about a radio button is how stupid they are. They have no brains. They do not know what
the other radio buttons are doing. You can layout six radio buttons and select everyone of them like they were toggles. That's
not the way we use radio buttons. They are supposed to be smart. They should know what to do if a radio button around them
is selected. They should turn themselves off because only one radio button in a group is supposed to be checked. That's
where radio_column and radio_row come in to play. They are the brains for the radio buttons. They watch all the buttons in
their row or column to make sure only one is turned on. Okay..moving on.
We will build a DCL file containing 4 radio_buttons plus an Okay and Cancel button. The selected item will be displayed
on the screen after the user presses the Okay button.
Layout thoughts: I will place the radio_buttons in a column, (stacked on top of each other). Then I'll put the Okay and
Cancel buttons in a row at the bottom of the dialog box. So...I'll need something like this:
: column {
: radio_column {
// Put code for radio_column here
: radio_column {
// Put code for radio_button 1 here
}
: radio_button {
}
: radio_button {
}
: radio_button {
}
}
: boxed_row {
: button {
}
: button {
}
}
}
SAMPLE5 : dialog {
: column {
: radio_column {
- 152 -
key = "mychoice";
: radio_button {
key = "but1";
label = "Apples";
}
: radio_button {
key = "but2";
label = "Oranges";
}
: radio_button {
key = "but3";
label = "Bananas";
}
: radio_button {
key = "but4";
label = "Lemons";
}
}
: boxed_row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
(defun C:SAMPLE5()


(progn
(exit)
)
)

- 153 -

(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
You should see this
C:Sample5
Command:
That doesn't look very good does it? Let's change the boxed_row into a boxed_column in our DCL file. (See the blue text in
the DCL file above) Make the changes then Save the Sample5.DCL file. No need to load the autolisp program again, it's
loaded. Just run the Sample5 program again. Now it should look like this:
- 154 -
It still doesn't look right. It's our label "Sample Dialog Box Routine - Part 5" that is causing the problem. Let's shorten it to
"SDBR - Part 5" and try it again:
Looks better!
Looking good so far. We need to add the SaveVars function to save the selected items from the radio_column when the
Okay button is pressed. Look at the blue text in the Sample5.lsp program above.
Let's steal the saveVars routine from the radio_column control on the "Saving data from the dialog box" page of this tutorial
and modify it. I'll show the modifications in red.
We can do this two different ways. We can check each radio_button to find out which one is on or we can check the entire
column of radio_buttons by getting the value of the radio_column.
First method: Checking the Radio_Column:
(defun saveVars()

;;; [ returns "but1" "but2" "but3" or "but4" whichever is selected.]
(setq myChoice(get_tile "mychoice"))
Second method: Checking each Radio_Button:
- 155 -
(defun saveVars()

(setq choice1(atoi(get_tile "but1"))) // 0 = not chosen 1 = chosen
Wow! That was easy. So...Which one do we use? For this tutorial, let's use both. Why not?
(defun saveVars()


Add this to the original Sample5.lsp program and we should have something that looks like this:
(defun saveVars()


(defun C:SAMPLE5()


(progn
(exit)
)
- 156 -
)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
display the selected item.

(if(= ddiag 2)
(progn
;;;--- Inform the user of his selection using the radio_column data
(princ "\n Using Radio_column data...You chose ")
(cond
((= myChoice "but1")(princ "Apples!"))
((= myChoice "but2")(princ "Oranges!"))
((= myChoice "but3")(princ "Bananas!"))
((= myChoice "but4")(princ "Lemons!"))
)
;;;--- Inform the user of his selection using the radio_buttons data
(princ "\n Using Radio_buttons data...You chose ")
(cond
((= Choice1 1)(princ "Apples!"))
((= Choice2 1)(princ "Oranges!"))
((= Choice3 1)(princ "Bananas!"))
((= Choice4 1)(princ "Lemons!"))
)
)
)
Add the above to the autolisp file, save it and test it out. Everything working okay?
- 157 -
Part 6 - Text and Toggles
Let's build a working DCL file showing us exactly how to handle text and toggles.
We will build a DCL file containing 4 toggles, one text, plus a Cancel button. The selected item will be displayed on the
screen in the text control.
Layout thoughts: I will place the text control on the top of the box. Then I'll put the toggles in a column, (stacked on top of
each other). Last, I'll put the Cancel button at the bottom of the dialog box. So...I'll need something like this:
: column {
: column {
: text {
// Put code for text here
}
}
: boxed_column {
- 158 -
: toggle {
// Put code for toggle 1 here
}
: toggle {
}
: toggle {
}
: toggle {
}
}
: boxed_row {
: button {
}
}
}
Let's copy in the code for the header and all of the controls above from the "Controls" section of this tutorial. I'll show the
changes that needed to be made in red. Notice the key names and labels had to be changed.
SAMPLE6 : dialog {
: column {
: column {
: text {
key = "text1";
value = "Nothing selected.";
}
}
: boxed_column {
label = "Choose your lucky charms:";
: toggle {
key = "tog1";
label = "Hearts";
value = "0";
}
: toggle {
key = "tog2";
label = "Moons";
value = "0";
}
: toggle {
key = "tog3";
label = "Stars";
value = "0";
}
: toggle {
key = "tog4";
label = "Clovers";
value = "0";
}
- 159 -
}
: boxed_row {
: button {
key = "cancel";
label = "Cancel";
is_default = true;
is_cancel = true;
}
}
}
(defun C:SAMPLE6()


(progn
(exit)
)
)


(start_dialog)


(if(= ddiag 1)
)

(if(= ddiag 2)
(progn
)
)

(princ)
Remove everything listed in orange above. We do not need an Okay button. Thus we do not need to check to see if the user
pressed Okay or Cancel. We also do not need the SaveVars routine in this program. Remove the orange items so your
program looks like the one below.
- 160 -
(defun C:SAMPLE6()


(progn
(exit)
)
)


(start_dialog)


(princ)
You should see this
C:Sample6
Command:
- 161 -
Doesn't look right. The dialog box is too wide. It's our label "Sample Dialog Box Routine - Part 6" that is causing the
problem. I would shorten it but, my text control will need the room if everything is selected. I'll have to display "Hearts
Moons Stars Clovers" all on one line. I'll leave it the way it is.
Notice you can select and deselect items without a problem but the text control doesn't change. We need to add the
action_tiles and function to accomplish this.
First let's write a routine to check each toggle and build a string representing all of the selected items.
(defun chkToggle()
(setq tog1(atoi(get_tile "tog1"))) // 0 = not chosen 1 = chosen

(setq myStr "")

(if(= tog1 1)(setq myStr(strcat myStr " Hearts")))
(if(= tog2 1)(setq myStr(strcat myStr " Moons")))
(if(= tog3 1)(setq myStr(strcat myStr " Stars")))
(if(= tog4 1)(setq myStr(strcat myStr " Clovers")))
;;;--- If nothing was selected...

(if(= myStr "")(setq myStr "Nothing Selected!"))
;;;--- Now set the text control to display the string

(set_tile "text1" myStr)
)
Alrighty then. I used the get_tile function to get the value of each toggle. I used the atoi function to convert that data from
a string to an integer. (I could have left it a string and checked to see if tog1 equalled "1" instead of the number 1.) I set the
variable myStr to an empty string and then appended all the checked toggle labels to it. I then changed the value of the text
control by using the set_tile function.
Add this to the top of your autolisp program and save it.
The last step is to add the action calls to the AutoLisp program. We need one action call per toggle switch. Each action call
should run the chkToggle function we just created.
(action_tile "tog1" "(chkToggle)")

Let's add this to the AutoLisp program. I'll show the new chkToggle function and the action calls in red. It should look like
this:
(defun chkToggle()
- 162 -
(setq myStr "")

(if(= tog1 1)(setq myStr(strcat myStr " Hearts")))
(if(= tog2 1)(setq myStr(strcat myStr " Moons")))
(if(= tog3 1)(setq myStr(strcat myStr " Stars")))
(if(= tog4 1)(setq myStr(strcat myStr " Clovers")))
;;;--- If nothing was selected...

(if(= myStr "")(setq myStr "Nothing Selected!"))
;;;--- Now set the text control to display the string

(set_tile "text1" myStr)
)
(defun C:SAMPLE6()


(if (not (new_dialog "SAMPLE6" dcl_id) ) (exit))


(start_dialog)


(princ)
Save it and test it out. Everything working okay?
- 163 -
PUTTING ALL TOGETHER
Now it is time to take all of the parts and pieces and put them together. Let's build a working DCL file that will let us see
most of the things we've learned and yet not get to deep into autolisp.
Lets draw a polygon or circle, on a selected layer with the option to save the settings last used for defaults next time we run
the program. If polygon is chosen, ask for the number of sides. So....we will need a list_box to hold all of the available layer
names. We will need a radio_column to select a circle or polylgon. We will need an popup_list to hold the number of sides
for the polygon. We will need a toggle to check the "Save Settings" option. And last, we will need an Okay and Cancel
button.
Layout thoughts: The list will need to have several layers showing so the user won't have to scroll forever. So, it will
probably be the tallest item on the dialog box. I'll put it in a column by itself. I'll try to fit the rest of the items in a column
beside it. Then I'll put the Okay and Cancel buttons at the bottom in a row. So...I'll need something like this:
: column {
: row {
: boxed_column {
: radio_column {
: radio_button {
// Put code for radio button 1 here [ Circle ]

}
: radio_button {
// Put code for radio button 2 here [ Polygon ]

}
}
: popup_list {
// Put code for popup_list here [ Number of Sides ]

}
: toggle {
// Put code for toggle here [ Save Settings ]

}
}
- 164 -
: row {
: list_box {
// Put code for list here [ Layer Names ]

}
}
}
: row {
: button {
// Put code for button 1 here [ Okay ]

}
: button {
// Put code for button 2 here [ Cancel ]

}
}
}
to be changed.
SAMPLE7 : dialog {
: column {
: row {
: boxed_column {
: radio_column {
key = "radios";
: radio_button {
label = "Draw Circle";
key = "drawcir";
value = "1";
}
: radio_button {
label = "Draw Polygon";
key = "drawpol";
value = "0";
}
}
: popup_list {
key = "numsides";
label = "Number of Sides";
width = 25;
}
: toggle {
key = "saveset";
label = "Save settings";
}
}
: row {
: list_box {
label ="Select Layer";
- 165 -
key = "layerList";
height = 5;
width = 15;
multiple_select = false;
value = "";
}
}
}
: row {
: button {
key = "accept";
label = " Okay ";
is_default = true;
}
: button {
key = "cancel";
label = " Cancel ";
is_default = false;
is_cancel = true;
}
}
}
Right click and copy the above. Open NotePad and paste it. Save the file as SAMPLE.DCL Be sure to change the
(defun C:SAMPLE7()


(progn
(exit)
)
)


(start_dialog)


(if (= ddiag 1)
(princ "\n \n ...SAMPLE7 Cancelled. \n ")
- 166 -
)

(if (= ddiag 2)
(princ "\n \n ...SAMPLE7 Complete!")
)

(princ)
You should see this
C:Sample7
Command:
Now type Sample and press enter. If everything went according to plan you should see this on your screen:
Notice there are no items in either list. We haven't added that part yet. Also notice the Draw Circle is selected. We did that
in the DCL file. We set the value of that radio_button to "1". We did not set the value of the toggle, so the default is
unchecked.
If you push the Cancel button the program will exit normally. If you press the Okay button an error will occur because we
have not defined the saveVars routine.
We have two things left to do. First we need to build the list for the popup_list control and the list_box control. Then we
need to add the list to the dialog box.
Instead of building a function to get all of the layer names into a list, let's just build the list manually to keep things simple.
Okay...you talked me into it. I'll do it both ways and you can use the one you want. I'm going to use the short version for this
tutorial.
Long way:
;;;--- Set up a list to hold the layer names

(setq layerList(list))
;;;--- Get the first layer name in the drawing
- 167 -
(setq layr(tblnext "LAYER" T))
;;;--- Add the layer name to the list

(setq layerList(append layerList (list(cdr(assoc 2 layr)))))
;;;--- Step though the layer table to get all layers

(while (setq layr(tblnext "LAYER"))
;;;--- Save each layer name in the list

(setq layerList(append layerList (list(cdr(assoc 2 layr)))))
)
Short Way:
(setq layerList(list "0" "DIM" "HIDDEN" "STR" "TX" "WELD"))
We also need a list for the polgon's number of sides:
(setq numSides(list "4" "6" "8" "12" "16"))
We need to add these lines to our autolisp program. Add it just below the new_dialog call and above the action_tile
statements.
We now need to upload the list into the dialog box. So put these lines just below the lines you just added.
;;;--- Add the layer names to the dialog box

(start_list "layerlist" 3)
(mapcar 'add_list layerList)
(end_list)
;;;--- Add the number of sides to the dialog box

(start_list "numsides" 3)
(mapcar 'add_list numSides)
(end_list)
When you are done it should look like this:
(defun C:SAMPLE7()


(progn
(exit)
)
)

(end_list)

- 168 -
(end_list)


(start_dialog)


(if (= ddiag 1)
)

(if (= ddiag 2)
)

(princ)
Save, Load, and Run. You should see this:
Next, let's build the SaveVars routine. We will do this by starting with the saveVars routine in the AutoLisp Model, then copy
and paste from the "Save Data from Dialog Box" section of this tutorial. We will then modify the names to match the key
names in the DCL file. I also changed a variable name to numStr to be used later to set the default settings. More on that
later. I'll show you the changes I made in red:
(defun saveVars()
(setq radios(get_tile "radios"))
;;;--- Get the number of sides selected from the list

(setq numStr(get_tile "numsides"))
(if(= numStr "")
(setq numSides nil)
(setq numSides(nth (atoi numStr) numSides))
)
;;;--- See if the user wants to save the settings

(setq saveSet(atoi(get_tile "saveset")))
;;;--- Get the selected item from the layer list

(setq sStr(get_tile "layerlist"))
(if(/= sStr "")
(progn
- 169 -

(setq layerName(nth sIndex layerList))
)

(progn

(setq sIndex -1)

(setq layerName nil)
)
)
)
Note: Since we did not specify a default value for the list_box, layerName will be set to nil if the user does not select a layer
from the list before hitting the Okay button.
Save, Load, and Run. Check the values after pressing the Okay button by typing an exclamation point and then the variable
name on the command line. Examples: To get the layer name type !layerName and press enter. To get the value of the
toggle type !saveSet and press enter. Everything working okay? Alrighty then...let's move on.
The only work left on the dialog box is to disable the "Number of Sides" popup_list when a circle is selected. Let's add two
action_tiles on both of the radio_buttons.

(action_tile "drawcir" "(toggleRadio 1)")
(action_tile "drawpol" "(toggleRadio 2)")
This will send a parameter of 1 to the toggleRadio function if the Circle is selected. It will send a parameter of 2 to the
toggleRadio function if the Polygon is selected. What the hell is a toggleRadio function?
We have to create it and put it in our AutoLisp program. Like this:
(defun toggleRadio(a)
;if circle is selected

(if(= a 1)
(mode_tile "numsides" 1) ;disable
;else
(mode_tile "numsides" 0) ;enable
)
)
Since our default for the radio buttons is to draw a circle, the numSides popup_list should be disabled before the dialog box
starts. So just before the action_tile statements we need to add this line:
(mode_tile "numsides" 1)
Copy, Save, and Run. You should see this:
- 170 -
The numSides popup_list is disabled when the circle is selected. Enabled when polygon is selected. Cool.
Here is the AutoLisp program after the lines above were added:
(defun saveVars()

(setq sStr(get_tile "numsides"))
(if(= sStr "")
(setq numSides nil)
(setq numSides(nth (atoi sStr) numSides))
)


(if(/= sStr "")
(progn


)

(progn

(setq sIndex -1)
- 171 -
)
)
)
(if(= a 1)
;else
)
)
(defun C:SAMPLE7()


(progn
(exit)
)
)


(end_list)

(end_list)


(start_dialog)


(if (= ddiag 1)
)

(if (= ddiag 2)
)

(princ)
- 172 -
)
Now the only thing remaining is to do something when the user presses the okay button. We have all of the dialog box data
stored in variable names....
Variable Name DCL Control Item Action Key Type of Data Stored
radios Radio_Column "radios" String [ Action Key Name]
numSides Popup_List "numsides" Integer [ Number of sides]
saveSet Toggle "saveset" Integer [ 0 or 1 ]
layerName List "layerlist" String [ Name of Layer]
So now all we have to do is write the AutoLisp code inside the "Okay button was pressed" IF statement. (Where the blue
line is above.)
Now we will replace the blue line above: (princ "\n \n ...SAMPLE Complete!") with new code.
First, let's go ahead and change the layer.
(setq oldLay(getvar "clayer"))

(setvar "clayer" layerName)
That was easy. Now, Let's draw the selected entity
(if(= radios "drawcir")

(progn
(setq pt(getpoint "\n Center point: "))
(command "circle" pt pause)
)
;;;--- Else draw a polygon
(progn
(setq pt(getpoint "\n Center Point: "))
(command "polygon" numSides pt "C" pause)
)
)
Add the above to your program and save it. Test it out. Everything working okay?
And finally all we have left is the code for the default settings. Since everything in the dialog box is a string, why don't we
save all of the data as strings. Lucky for us, AutoDesk included 15 setvars for us to store data in. USERR1 thru USERR5 is
used to store real numbers. USERI1 thru USERI5 is used to store integers. USERS1 thru USERS5 are used to store strings.
We will use the system variables USERS1 thru USERS4 to save our data since we are saving the data as strings. All of these
setvars are stored inside the drawing file. They will be there everytime you open your drawing. How convenient! So let's get
to it.
The first variable to store is RADIOS and it is already a string. So....
(setvar "USERS1" radios)
- 173 -
The second variable to store is NUMSIDES and it is an integer representing the number of sides the polygon should have. I
want to store the index of the selected item in the list not the actual number of sides. We saved the index as a variable named
NUMSTR when we ran the saveVars routine. So...
(setvar "USERS2" numStr)
The third variable to save is SAVESET. It is stored as an integer. We will have to convert it to a string to save it.
(setvar "USERS3" (itoa saveSet))
The fourth and final variable to save is LAYERNAME. It is stored as a string. I want to save the index of the selected item.
We saved that earlier with the saveVars routine in a variable named sSTR.
(setvar "USERS4" sSTR)
The last thing we have to do is check for the default settings and load them if they exist.
(defun saveVars()

(setq numStr(get_tile "numsides"))
(if(= numStr "")
(setq numSides nil)
(setq numSides(nth (atoi numStr) numSides))
)


(if(/= sStr "")
(progn


)

(progn

(setq sIndex -1)

)
)
)
(if(= a 1)
- 174 -
;else
)
)
(defun C:SAMPLE7()


(progn
(exit)
)
)
;;; Build the list for the dialog box


(end_list)

(end_list)
;;;--- Add the code here to check for defaults

(if(/= (getvar "USERS1") "")
(progn
(setq radios (getvar "users1"))
(setq numStr (getvar "users2"))
(setq saveSet(getvar "users3"))
(setq layerIndex(getvar "users4"))
(set_tile "radios" radios)
(set_tile "numsides" numStr)
(set_tile "saveset" saveSet)
(set_tile "layerlist" layerIndex)
)
)
;;;--- Only disable the numSides popup_list if a circle is being drawn

)


(start_dialog)


(if (= ddiag 1)
- 175 -
)

(if (= ddiag 2)
(progn
;;;--- Save the old layer and reset to new layer

(setq oldLay(getvar "clayer"))
(setvar "clayer" layerName)
;;;--- See what needs to be drawn

(progn
(setq pt(getpoint "\n Center point: "))
(command "circle" pt pause)
)
;;;--- Else draw a polygon

(progn
(setq pt(getpoint "\n Center Point: "))
(command "polygon" numSides pt "C" pause)
)
)
;;;--- See if we need to save the settings

(if(= saveSet 1)
(progn
;;;--- Add code here to save the settings as defaults

(setvar "USERS1" radios)
(setvar "USERS2" numStr)
(setvar "USERS3" (itoa saveSet))
(setvar "USERS4" sSTR)
)
)
)
)

(princ)
- 176 -

Alisp

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Alisp

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alisp

Uploaded by

Copyright:

Available Formats

The AutoLisp Beginner

Let's get to it. But how?

The first thing you should know about AutoLisp:

AutoLisp always has as many opens "(" as it does closes ")".

Every AutoLisp program should look similar to this:

Some safe examples of variable names are:

Some bad examples are:

(setq car 12)

(setq cdr 400)

Again with the car and cdr stuff? What is it man?

A couple of important last minute things:

Okay, enough for variables for now. Let's move on.

Ex. (defun myProg() or (defun C:myProg()

(defun myProg()(princ "Jeff")) and press enter.

You should see something that looks like this:

(defun myProg()(princ "Jeff")(princ))

(defun C:myProg()(princ "Sanders")(princ))

Click on the Start button. Go to Programs. Go to Accessories. Go to NotePad.

Notepad should open. When it does, type in:

An example of this is (defun C:myProg(/ varA varB varC).

The AutoLisp Intermediate Tutorial

A string is an AutoLisp data type consisting of alphanumeric characters inside quotes.

eg. "Jeff" "Sanders" "1245r" "3"

An integer is a number without a decimal place.

eg. 1 23 456 67890 -5 -687

A real number is a number that has a decimal place.

eg. 1.0 23.034 456.2 -56.345

eg. (1 2 3) ("Jeff" 156.0 45.0 3 "Sanders") (1) () ( (1 2 3) (4 5 6)("A" "B" "C") )

String Functions substr strlen strcase strcat

Number Functions abs atof atoi fix float itoa

Group Codes/Associated List assoc Entity_DXF_Group_Codes

Conversion Functions fix float itoa atoi atof rtos angtos

Math Functions + - * / +1 -1 cos atan sin sqrt expt

Selecting Entities entsel ssget

Selection Set Functions ssadd ssdel sslength ssname

Entity Functions entget entlast entnext entdel entmod entupd

File Functions open close read-line write-line New!

DXF Group Code Table

substr - This function retrieves part of a string.

Syntax : (substr "string" startPoint numberOfCharacters)

numberOfCharacters - an integer or variable representing an integer that corresponds to the length of

(substr "Jeff Sanders" 1 6) would return "Jeff S"

(substr "Jeff Sanders" 6 3) would return "San"

(substr "Jeff" 6 4) would return ""

(substr "" 9 3) would return ""

(substr "Jeff Sanders" 9) would return "ders"

strcase - This function converts to upper or lower case.

Syntax : (strcase "string" flag)

flag - a flag that sets uppercase or lowercase.

T = True nil = False

T = LowerCase nil or empty = UpperCase

(strcase "Jeff" T) returns "jeff"

(strcase "Jeff" nil) returns "JEFF"

(strcase "123a" nil) returns "123A"

(strcase "" nil) returns ""

(strcase "Jeff") returns "JEFF"

Syntax : (strlen "string")

(strlen "Jeff") returns 4

(strlen "Jeff Sanders") returns 12