Sounds like it has commands outside of the defined function (defun) - post it on here and I should be able to sort it for ya![]()
Registered forum members do not see this ad.
I finally found which lisp is causing me problems on my startup suite. Can anyone who knows something about lisp tell me why when this lisp loads it asks for me to select object to scale and stops the rest of the lsps in the startup suite from loading. any help would be great
Code:;; This lisp breaks a two lines which cross each other (defun c:sc () (setq pick (entsel "\nPick:")) (terpri) (setq pnt (getpoint "\nPick point:" )) (terpri) (setq scl (getstring "0.5")) (command "scale" pick pnt scl ) ) (defun c:half () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.5) ) (defun c:twice () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 2) ) (defun c:1QUARTER () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.25) ) (defun c:three4 () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.75) ) defun c:alberto () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 1.5) ) This one aaa lets you scale reference (defun c:aaa () (command "OSNAP" "ins") (SETQ object (entsel "\n pick object")) (SETQ INS (GETPOINT "\NPICK POINT")) (command "scale" object "" INS "R" "6-1/64" "4.5") (command "osmode" "0") ) (defun c:vsc () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt tom) ) (defun c:t0 () (command "style" "" "" 0 "" "" "" "" "")) )
Last edited by chelsea1307; 30th Mar 2009 at 10:10 pm.
"The problem is stupidity. I am not saying there should be capital punishment for stupidity, but, why don't we just take the safety labels off of everything and let the problem solve itself? "
Sounds like it has commands outside of the defined function (defun) - post it on here and I should be able to sort it for ya![]()
Lee Mac Programming
With Mathematics there is the possibility of perfect rigour, so why settle for less?
Just another Swamper
oops, i meant to post that origionally
"The problem is stupidity. I am not saying there should be capital punishment for stupidity, but, why don't we just take the safety labels off of everything and let the problem solve itself? "


try this it has a few problems
Code:;; This lisp breaks a two lines which cross each other (defun c:sc () (setq pick (entsel "\nPick:")) (terpri) (setq pnt (getpoint "\nPick point:" )) (terpri) (setq scl (getstring "0.5")) (command "scale" pick pnt scl ) ) (defun c:half () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.5) ) (defun c:twice () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 2) ) (defun c:1QUARTER () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.25) ) (defun c:three4 () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.75) ) (defun c:alberto () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 1.5) ) ;;This one aaa lets you scale reference (defun c:aaa () (command "OSNAP" "ins") (SETQ object (entsel "\n pick object")) (SETQ INS (GETPOINT "\NPICK POINT")) (command "scale" object "" INS "R" "6-1/64" "4.5") (command "osmode" "0") ) (defun c:vsc () (prompt "\nPick entities you want to scale: ") (setq ss (ssget)) (setq pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt tom) ) (defun c:t0 () (command "style" "" "" 0 "" "" "" "" ""))
After quick glance - just tidied em up a bit:
[a few could be written better imo]Code:(defun c:sc (/ pick pnt scl) (setq pick (entsel "\nPick:") pnt (getpoint "\nPick point:") scl (getstring "0.5")) (command "scale" pick pnt scl) (princ)) (defun c:half (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.5) (princ)) (defun c:twice (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 2) (princ)) (defun c:1QUARTER (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.25) (princ)) (defun c:three4 (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 0.75) (princ)) (defun c:alberto (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt 1.5) (princ)) (defun c:aaa (/ object ins) (command "OSNAP" "ins") (SETQ object (entsel "\n pick object") INS (GETPOINT "\NPICK POINT")) (command "scale" object "" INS "R" "6-1/64" "4.5") (command "osmode" "0") (princ)) (defun c:vsc (/ ss pt) (prompt "\nPick entities you want to scale: ") (setq ss (ssget) pt (getpoint "\n Pick scale point: ")) (command "scale" ss "" pt tom) (princ)) (defun c:t0 () (command "style" "" "" 0 "" "" "" "" "") (princ))![]()
Lee Mac Programming
With Mathematics there is the possibility of perfect rigour, so why settle for less?
Just another Swamper
i know... i didnt write any of these, i dont even use these... my office is afraid of change, even though i dont think anyone uses these anymore if i get rid of a file they freak, so i figured i would try to get it so it works without causing problems...
"The problem is stupidity. I am not saying there should be capital punishment for stupidity, but, why don't we just take the safety labels off of everything and let the problem solve itself? "
Lee Mac Programming
With Mathematics there is the possibility of perfect rigour, so why settle for less?
Just another Swamper
I actually have it the other way, my company is somewhat nudging me to learn C++ so I can maintain our scripts (for add-on hasbCAD) in the event my colleague (who writes said scripts) should succumb to the "hit by a bus" scenario. Unfortunately, the only actual coding I've ever done was making my Tandy beep out the Für Elise in QBASIC...
Just because you're, doesn't mean wrong is all that's
.




There's a designer (sic) here with 15+ years experience w/ cadd that refuses to use anything that isn't OOTB; no lisp, no pgp, he has to pick the commands from icons, he won't even use the wheel on his mouse to pan/zoom. It's hard to try to implement anything progressive (e.g. annotative text, dynamic blocks) when people refuse to try and learn. To each their own I guess...
Oops, I didn't mean to hijack the thread.
Registered forum members do not see this ad.
glad to know im not alone with this
"The problem is stupidity. I am not saying there should be capital punishment for stupidity, but, why don't we just take the safety labels off of everything and let the problem solve itself? "
Bookmarks