lisp solutions

[kibber]

I modified a lisp routine which allows for a standardized system of page setup names to be loaded into each drawing with a keystroke. The guys in my office didn't want to have to remember the three letters I designated as the keystroke, so I added it to the acad.lsp for an autoload when you open a new drawing.
It works perfectly for retrofitted drawings, the only problem arises when you open a drawing which already has it in place. When I load one of those I get this prompt-
Regenerating model.
._-PSETUPIN Enter file name: M:/PROJECT
STANDARDS/ACADSUPPORT/PLOTCONFIG/FJR-plotconfig.dwg Enter user defined page
setup(s) to import or [?]: *
Page setup "1117-COM_INT" already exists. Redefine it? [Yes/No] <N>:

we have close to 20 setups so it gets annoying.
anyone know a lisp script to override or ignore or even auto redefine?

this is all I have for a script right now
(command "._-PSETUPIN" "M:/PROJECT STANDARDS/ACADSUPPORT/PLOTCONFIG/FJR-plotconfig.dwg""*")

thannks for your help

[CADTutor]

I imagine that you can get the LISP routine to check if the setup has already been made using an if statement. Can't give details because my LISP is a little rusty but I'm sure someone else here can help.

[kibber]

Thanks for your input CADtutor, I'd like to learn the "if" command too, basically I got around it with adding "y" 17 times to the end of my lisp.

if anyone has an example of using the if command to answer a string of redefine prompts I'd love to see it.

By the way, after loading a few lisp routines I've now got tiny little cross hairs when I left click they stay on the screen until I refresh or zoom. They appear with every click.
If anyone has seen this or has an idea how to get rid of them it would be great
Thanks

[Kate M]

Appearing crosses sounds like blipmode -- maybe one of your lisps turned it on?

[CADTutor]

Appearing crosses sounds like blipmode -- maybe one of your lisps turned it on?

Agreed, type BLIPMODE at the command prompt and turn it off.

[kibber]

blipmode...good stuff now its off.
I guess the only thing left is to figure out which lisp turned it on

thanks for the help guys, it was really getting annoying.

[vizwhiz]

hi There

Kibber

maybe you could add a line (The Last Line) of acad.lsp to be

****

(setq bm (getvar "blipdmode"))
(setq bm (setvar "blipmode" 0))

****

This should catch (but not solve The Problem) the blipping blipmodes

****

Thanks

Randy