save lisp parameters for next use
Define the variables if they are not present.
So next time when you run the code, you can retrieve that value.
Example:
(defun setmyvariables () (if (and myvar1 myvar2) (progn (print "variables found") (print myvar1) (print myvar2) );progn (progn (print "variables not found, setting now") (setq myvar1 10 myvar2 20) );progn );if );defun
Also if you need to save these variables for another drawings or even in a new AutoCAD session try setenv and getenv
| 
| 
@Ajilal.Vijayan wrote:
....
.... (if (and myvar1 myvar2) ....Also if you need to save these variables for another drawings or even in a new AutoCAD session try setenv and getenv
[A small quibble, perhaps, and I know it's just a generic example, but.... In that situation, if one of those two variables has a value in it but not the other, both will be set to the built-in values, possibly changing the value already in the one variable. If that might be an issue, it's easily avoided with slightly more code, by doing the same for each variable separately instead of together.]
There are countless examples around of the use of global variables for this kind of thing within the same session in the same drawing. For just a couple, see my routine for labeling entities and breaking them around the labels, here, and another similar one that masks instead of breaks the labeled entities. Routines can be written with built-in standard initial-default values similarly to Ajilal.Vijayan's example, or to have no initial defaults, but to always ask the User for a value on first use, to become the default that will be offered on subsequent use.
For some examples of Ajilal.Vijayan's suggested use of environment variables, so that the values are available not only the next time you use the command in the current drawing but in any drawing, and are remembered even after closing and getting back into AutoCAD, I wrote some routines that use that approach to save multiple Fillet radii and multiple Chamfer distances.
[Most of the cited examples are around these Forums somewhere -- it's just easier for me to find them on the Cadalyst CAD Tips site.]
Kent Cooper, AIA 
@Anonymous wrote:
hi. is there any way to save and read last used lisp parameters every time it's used? for example: the offset command "remembers" the last offset distance and layer options parameters used. i'd like to have 2 saved parameters in my file if possible.
Hi ilan7YZJH,
if by 'my file', you mean the current dwg file, this System Variables, are intended for user use, and saved in the Drawing...
USERI1 to USERI5 to store integer values
USERR1 to USERR5 to store real numbers
ex.
(if (setq myvarname (getdist (strcat "\nSpecify Distance <" (rtos (getvar 'USERR4) 2 2) ">: ")))
(setvar 'USERR4 myvarname)
(setq myvarname (getvar 'USERR4))
)
Hope this helps,
Henrique
@hmsilva wrote:
....
if by 'my file', you mean the current dwg file, this System Variables, are intended for user use, and saved in the Drawing...
USERI1 to USERI5 to store integer values
USERR1 to USERR5 to store real numbers
....
In addition to those, there are also similar variables available for User-specified text Strings: USERS1 through USERS5. But they are usable only within the same editing session in a drawing -- for some unknown reason, they are not saved in the drawing file, as the Integer and Real number variables are.
Kent Cooper, AIA
@ВeekeeCZ wrote:
@Anonymous wrote:
thanks everyone for the suggestions. i'll clear one thing up: by "my file" i meant the lisp and not the drawing. the ideal for me will be that settings are kept even for different sessions, so i'll have a look into setenv and getenv.
...
If you can modify your lisp... so why not to use some exteral file to store all old values of all variables you need?
You can have some oldvariables.txt stored next to your routines where you gonna have pair of name and values
VARIABLE1 VALUE1
VARIABLE2 VALUE2
Why not Ajilal's advice, setenv and getenv...should be easier to write and read.
ex.
(if (not (setq VARIABLE1 (getenv "VARIABLE1")))
(progn
(setenv "VARIABLE1" "1.00") ; change to the correct default value
(setq VARIABLE1 (getenv "VARIABLE1"))
)
)
(if (setq myvarname (getdist (strcat "\nSpecify Distance <" (getenv "VARIABLE1") ">: ")))
(setenv "VARIABLE1" (rtos myvarname 2 2));change the precision if necessary
(setq myvarname (read (getenv "VARIABLE1")))
)
Henrique
@Anonymous wrote:
can i also make that the status bar will display available parameters with highlighted trigger letters, similar to the built-in commands? again an example from the offset command: the through, erase and layer parameters are available with T, E and L highlighted in blue, respectively.
Normally the command options are set by using getkword & initget. ( and its not in the status bar but in the command prompt)
I just tried with one example and like in the built-in commands the options are not highlited neither the keywords are in blue.
So I am not sure how we can do this.
Kent1Cooper wrote
Spoiler
[A small quibble, perhaps, and I know it's just a generic example, but.... In that situation, if one of those two variables has a value in it but not the other, both will be set to the built-in values, possibly changing the value already in the one variable. If that might be an issue, it's easily avoided with slightly more code, by doing the same for each variable separately instead of together.]
Thanks for pointing out that @Kent1Cooper, like you mentioned my intention was to show an example to @Anonymous.
@scot-65 wrote:
There could be other methods.
I know that I'm speaking up a bit late, but I have at one point in time or another tried all of those options through the years, and my experience is that the one option not mentioned seems to be the most convinient. Custom Drawing Properties are simple to work with and can be added and altered without any code if necessary.
I'm just sayin', it works best for me. 