Hatch Target lisp
Accepted solution
@Anonymous wrote:
.... ;Hatch Target (command "hatch" "ansi31" "1" "0" "@" "0.25" "@" "0.25" "@" "0.25" ) ....
Welcome to these Forums!
Your Hatch command is questionable about selection of those Circles to Hatch them. If these entries:
"@" "0.25" "@" "0.25" "@" "0.25"
are supposed to be object selection, it's a peculiar way to do it, the first "@" entry won't find a Circle because it will be at the center, and could find something other than one of the Circles, the other "@" entries don't add anything, and the "0.25" entries work with the direction toward the cursor at the time, so what if it remains at the center location [no direction]? Try:
"@0.25,0"
three times instead, or
"@0,0.25"
or
"@0.25<0"
or any valid point designation that's sure to land on the Circles. And finally, you don't complete the selection of items to Hatch -- you need an Enter "" to do that. Try something like this [untested]:
(command "hatch" "ansi31" "1" "0" "@0.25,0" "@0.25,0" "@0.25,0" "")
[And by the way, that's not a "script" -- that word has a specific and different meaning in AutoCAD.]
Kent Cooper, AIA 
@Anonymous wrote:
....
I should format my code -
To make it easy to read?
Ok,
Do you mean easer to read then this
defun C:Target (/ ce cp) (setq ce (getvar "cmdecho")) ;capture current environment variables (setvar "cmdecho" 0) ;suppress command echo (setq cp (getpoint "\nCenter point: "));get start point and draw Inner circle (command "_circle" cp "_D" 0.5) (command "_circle" cp "_D" 1) ;draw second circle (command "_circle" cp "_D" 1.5) ;draw outer Circle (command "_.-hatch" "_p" "ansi31" 0.25 0 "_s" (entlast) "" "" );Hatch Target (setvar "cmdecho" ce) ;silent exit (princ) )
???
I'm sure the software can read it with no problem,
....
"Please use {i} insert code - before posting"
I'm not sure what this is at all,
....
Just to touch on those two:
If you were to put that code as it came through into a .lsp file, it would not work, i.e. no, the software would not be able to read it. A semicolon is a "comment" marker, and it and everything following it on the same line will be ignored, which in this case includes a lot of your operational code. And most lines start with elements that would be invalid as the beginning of a line of AutoLisp code. And yes, the breakdown into logical lines also makes it easier, even for experienced code writers, to be able to discern what it's supposed to do.
I'm not sure why some people paste code in that's originally in separate lines but it comes out all strung into one continuous paragraphs like that -- it may be browser related or something. But the following may be relevant:
The { i } is the Insert-Code "button" on the tool bar [between the Spoiler and Emoticon buttons]. If you pick on it and paste your code into that window instead of into the "body" of a message, I think [I'm not positive this is true in all circumstances] that it will retain its line breakdown, solving the first issue at the same time. It will also retain any indentation [which also sometimes disappears when pasting into the message body], which is also an aid to understanding code structure.
Kent Cooper, AIA
