Search this Forum for things like "tutorials" or "learn AutoLisp", and you will find many website links, book titles, and so on that can get you going.
I'm afraid I don't completely understand the questions, but here goes....
1) I'm not sure what "object oriented" really means. Other people more familiar with the term would be able to help more than I can. AutoLisp can certainly do many things that are not specific to "objects," so the answer may be No, but many of its functions do work on drawing entities, if that means that the answer is [partially?] Yes. Some drawing entities represent "objects," but many do not, if that suggests an answer.
2) What do you mean by "in main program"? In AutoCAD, yes, you can define functions [that's one of the main things AutoLisp is used for], if that's what you mean, but usually by way of something else, such as a text editor outside AutoCAD, or the Visual Lisp console [VLIDE], which operates from inside AutoCAD but has its own distinct way of working, so it's not really "in the main program" in the same way as other operations. If you mean "Can I add a function into the 'core' AutoCAD program itself?", the answer is No, but you can make your own functions and commands, and have them automatically loaded in every drawing, which should be effectively the same.
3) Does the word "not" belong in that question? Assuming it should not be there, the short answer is Yes, but by "function" do you mean AutoLisp's internal functions themselves, or a function defined using AutoLisp? Yes, you can call AutoLisp functions from within other functions -- a very simple example:
(setq Point1 (getpoint "\nPick point: "))
And you can call functions defined using AutoLisp [with the (defun) function] from within other functions, by putting the defined function's name in parentheses.
Go to the Customization Guide and some of the tutorials and website links that you will find with a Search as suggested before, and put some time into it, and your basic questions will be answered.
@Anonymous wrote:
....
1)
a)If I draw a box, can I treat it like an object?
I mean can I change its properties (like in properties menu) by specifying the Width parameter in my function?
b) If have helix and I used sweep tool, is there way to treat it as an object. Can I specify or change its height, like I use stretch command ?
2) What do you mean by "in main program"?
I mean the following:
Let's say I have this function
(defun C:function1 (/ pl p2 p3 p4)...... )
is there way to define function inside this function and call it when I need it
....
1) There are different ways to draw many things, but some of them would be considered objects in that way. a) A box drawn as a 1-unit cube and defined as a Block can be Inserted at whatever scale factors you need for its size, and the scale factors can be changed in the Properties box. PRESSPULL can be used to adjust the size of various kinds of things. Dynamic Blocks are another way to get changeable properties. In some of the overlay discipline-specific programs, there are special kinds of objects not available in plain AutoCAD -- for example in the Architectural overlay, there are walls that know they are walls, and windows that know they are windows, and when you put a window into a wall, the wall automatically has the appropriate hole cut in it, and if you move the window, the hole in the wall moves with it, etc. b) A helix can be played with in that way, but I'm not sure about what you get from Sweeping something along it [I'm at my older-version location at the moment, without either Helix or Sweep commands available]. If the result is a 3D Solid as it is from Extruding something along it, that would not be adjustable as you describe, but someone with a newer version could answer for a Sweep result.
2) Yes -- this is done all the time, with the internally-defined function commonly referred to as a "subroutine."
LISP is not object oriented, but there are some functions provided for accessing methods and properties of COM/ActiveX objects. Otherwise its a lot like F# in structure, being functional rather than imperative in style.
LISP cannot create arbitrary drawing objects, it can only work with already established AutoCAD objects.
AutoCAD 3D solids are not parametric, so they cannot be easily modified.
There is no concept of scope in LISP - everything is "global" with the exception that functions can localize some variables. That includes functions, so creating a (defun foo ( arg1 arg2 ) ... ) function would be available inside all other functions as (foo "TEST" 1) using appropriate arguments.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you don't want to just copy the fret Lines and scale them as I suggested when I posted that drawing, it can certainly be automated. Do you need to do this often enough that a routine is really worthwhile? Even if not, just as an exercise, here is one way. I did the drawing by repeatedly setting the Offset distance for each fret and Offsetting the Bridge Line each time, but for an automated routine it seemed a little easier to do it by repeated Copying, though Offset could certainly be used instead.
(defun C:FRETS (/ fret bridge neck b1 n1 len ang i)
(defun fret (n) (/ len (expt (expt 2 (/ 1.0 12)) n)))
(setq
bridge (car (entsel "\nSelect BRIDGE Line: "))
neck (car (entsel "\nSelect NECK-end Line:"))
b1 (vlax-curve-getStartPoint bridge)
n1 (vlax-curve-getClosestPointTo neck b1 T)
len (distance b1 n1)
ang (angle b1 n1)
); setq
(repeat (setq i 20); <-- can do more than 20 if desired
(command "_.copy" bridge ""
"_none" b1
"_none" (polar b1 ang (fret i))
); command
(setq i (1- i))
); repeat
(princ)
); defun
(vl-load-com); [if needed]
(prompt "\nType FRETS to draw frets between bridge and neck-end Lines.")
That requires the Bridge and Neck-end Lines to be drawn already, and to be in the proper relationship to each other. It could also be done in a way that would draw those Lines within the routine, asking the User only to specify the distance between them, and if you like a direction and/or location. And of course it could be made to verify that Lines were actually selected and properly aligned, and that the Bridge Line is not on a locked Layer, use [and make if necessary] a specific Layer, etc.
s.shivaprem wrote:....
Thanks for your last post!
I am still not so good with AutoLisp,but you gave me the direction on what I need to learn, what commands I should learn.
....
You're welcome. A good exercise for you, that should not be too difficult for a beginner, would be to figure out how to make it do the frets using Offset instead of Copy.
