So, with the recent post on geomarkervisibility and the suggestion to set that variable in the acaddoc.lsp file, what else do people have set in there? Some things I've thought about:
filedia=1
cmddia=1
geomarkervisibility=0
ltscale=1
psltscale=1
msltscale=1
pickfirst=1
pickadd=2
navcubedisplay=1
Any others?
p.s. want to mess with somone? Set ZOOMWHEEL to 1. 🙂
I include all of those except the navcubedisplay. I also have:
(vl-load-com) ;;to allow vlisp routines to run without needing it in every lisp I load
When I was using lisp to program with I had a number of helper utilities that I loaded as well.
Now, you have to understand that I don't have any of those in my acaddoc.lsp file but if I were in a production environment, those definitely would be there.
As for the navcubedisplay, I find the navcube to be pretty useless unless you are in a 3D envirnonment.
This is mine......
(setvar "attdia" 1)
(setvar "cmddia" 1)
(setvar "filedia" 1)
(setvar "pickfirst" 1)
(setvar "VISRETAIN" 1)
(setvar "UCSICON" 1)
(setvar "TRANSPARENCYDISPLAY" 1)
(setvar "geomarkervisibility" 0)
(setvar "OSMODE" 4259)
(setvar "osnapz" 1)
(setvar "SKPOLY" 1)
(setvar "DRAWORDERCTL" 1)
(setvar "EDGEMODE" 1)
neilyj (No connection with Autodesk other than using the products in the real world)
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@BrianHailey wrote:So, with the recent post on geomarkervisibility and the suggestion to set that variable in the acaddoc.lsp file, what else do people have set in there? Some things I've thought about:
filedia=1
cmddia=1
geomarkervisibility=0
ltscale=1
psltscale=1
msltscale=1
pickfirst=1
pickadd=2
navcubedisplay=1
Any others?
p.s. want to mess with somone? Set ZOOMWHEEL to 1. 🙂
This one got me....actually NAVVCUBEDISPLAY....!!!!
neilyj (No connection with Autodesk other than using the products in the real world)
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Mine's simple:
(SETVAR "AUTOSNAP" 5)
(SETVAR "OSMODE" 1)
(SETVAR "OSNAPNODELEGACY" 1)
I'll look in to including some others from this thread.
Allen
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@BrianHailey wrote:
..... in the acaddoc.lsp file, what else do people have set in there?
Nothing that changes DBMOD from 0.
After reading this thread this is what I've decided to use:
(SETVAR "AUTOSNAP" 5)
(SETVAR "OSMODE" 1)
(SETVAR "OSNAPNODELEGACY" 1)
(SETVAR "CMDDIA" 1)
(SETVAR "FILEDIA" 1)
(SETVAR "PICKFIRST" 1)
(SETVAR "VISRETAIN" 1)
(SETVAR "GEOMARKERVISIBILITY" 0)
(SETVAR "SKPOLY" 1)
Allen
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Since the acaddoc.lsp file gets overwritten if I do a repair/re-install, I put all my settings in a acad.lsp and in the Options set it to load with every drawing. I have my acad.lsp file stored on a network in my user folder, and I have that folder in my support paths.
Here is our acaddoc.lsp shared to all.
(if (not (zerop (getvar "mirrtext")))(setvar "mirrtext" 0))
(if (not (zerop (getvar "plinegen")))(setvar "plinegen" 1))
(if (not (zerop (getvar "filedia")))(setvar "filedia" 1))
(if (not (zerop (getvar "cmddia")))(setvar "cmddia" 1))
(if (not (zerop (getvar "pellipse")))(setvar "pellipse" 1))
(if (not (zerop (getvar "plinetype")))(setvar "plinetype" 2))
(if (not (zerop (getvar "geomarkervisibility")))(setvar "geomarkervisibility" 0))
(LOAD"PLJOIN")
John Mayo
@LisaPohlmeyer wrote:
Since the acaddoc.lsp file gets overwritten if I do a repair/re-install, I put all my settings in a acad.lsp and in the Options set it to load with every drawing. I have my acad.lsp file stored on a network in my user folder, and I have that folder in my support paths.
Lisa, this file never gets altered by repair/reinstall/update (or it shouldn't, mine doesn't). Both acad.lsp and acaddoc.lsp files are for the sole use of end-users. The acad2***.lsp and acaddoc2***.lsp files DO get replaced and are highly recommended to avoid placing any customizations into becuase of that.
I've used the same acaddoc.lsp file for years (adding & removing things along the way) in my AcadLisp folder. This way I just need to add that folder to the support path whenever I get a new version.
@LisaPohlmeyer wrote:
Since the acaddoc.lsp file gets overwritten if I do a repair/re-install, I put all my settings in a acad.lsp and in the Options set it to load with every drawing. I have my acad.lsp file stored on a network in my user folder, and I have that folder in my support paths.
That is incorrect.
"acad.lsp" and "acaddoc.lsp" are USER files are will never be overwritten by AutoCAD.
You are thinking of "acad20xx.lsp" and "acad20xxdoc.lsp" - these are PROGRAM files and may be overwritten.
IMO - you should use "Acad.lsp" to load things [per session] and use "acaddoc.lsp" to load things [per drawing].
"IMO - you should use "Acad.lsp" to load things [per session] and use "acaddoc.lsp" to load things [per drawing]."
That's how we do it. Although I have seen very little use for us in placing things in acad.lsp. All those things seem to work better for us if we force load them with each new dwg.
John Mayo
@Anonymous wrote:
..... I have seen very little use for us in placing things in acad.lsp.
Yes, it's fairly small. Generally, setting global variables that other routines need, setting the support file search path(s), setting registry saved setvars, and loading things that only need to be loaded once per session (mditabs.arx)
Oh yes Randy there is a real need for that file just not in our small work environment with very few addon apps. I didn't mean to sound like acad.lsp is useless. The keywords were, 'for us'. 🙂
I could probably load pljoin in acad.lsp but it's easier for me to port, update, etc with only one file.
John Mayo