LISP Routines misbehaving (see
Hi guys,I am just getting some weird behavior with some of my LISP routines, the best way to explain it would be - they don't work like they usually do.
For example, I have a routine with part code as below:
(command "copybase" rvpt1 sset "" "ucs" "w" "pasteblock" rvpt2 "explode" "L" "move" "p" "" rvpt2 pause)
Which had been working fine for years, until today.Now I must change the code to:
(command "copybase" rvpt1 sset "" "ucs" "w" "pasteblock" rvpt2 "explode" "L" "" "move" "p" "" rvpt2 pause)
..in order for the routine to work.
Has anyone else every had this type of thing happen?I can't help but think there may be some system variable that controls how commands behave within LISP routines, and I have accidently changed it.
Thanks a lot for any help, looking forward to hearing back. This I would consider to be correct as Explode like lots of others you can pick multiple entities so must use a "" to say all done, the variable will be something to do with pick singular or multiple.Try Pickadd 0 1 2 Hi BigAl,
Thanks for the reply.I have managed to correct theissue by running a system restore.This unfortunately makes it hard toexperiment with other possible solutions, but I really needed theinstant fix.
I tend to agree that I would expect to need to enterthe "" after feeding the selection set to the EXPLODE command.I hateto be argumentative, but I had noticed in the past that executingEXPLODE through a LISP routine doesn't require the "" in order for it towork (which I find strange, but perhaps there is some explanation). For example, if I draw a polyline, then enter (command "explode" "L") at the command line, the polyline will happily be exploded down to a line, but if I enter (command "explode" "L" "") after drawing a polyine - the polyline will be exploded, and then the PLINE command will be initiated. Ensure QAFLAGS is set to 0 Hi Lee,
Thanks for the reply.
Yep, that did it. Those undocumented system variables... Get me every time.
Thanks again. You're welcome!
页:
[1]