topic Betreff: Basic autolisp question in Visual LISP, AutoLISP and General Customization Forum

Basic autolisp question

Anonymous — Mon, 11 Jun 2018 22:42:31 GMT

I have a list of pairs in autolisp ((x1 x2)(x3 x4)(x6 y5)...) This list contains variable number of argument and I wonder on how can feed all the arguments to the command funct.

(command "xxxx" pair1 pair2 ... pairfinal)

Betreff: Basic autolisp question

cadffm — Mon, 11 Jun 2018 22:47:56 GMT

The answer is depent of the whole command expression, but for normal:
(Command "point")
(Foreach pair ofmylist (command pair))
(Command "")

Which command you try to use in (command expression?

Betreff: Basic autolisp question

Anonymous — Mon, 11 Jun 2018 22:58:06 GMT

I attached the detail in a notepad

Betreff: Basic autolisp question

cadffm — Mon, 11 Jun 2018 23:32:25 GMT

Oh select is very special (simular to the alltime autocad object selection)

Three answeres

(foreach coord ofmylist (command coord))

If your setting is the standard setup (pickauto) it should working.

BUT the autocad object selection is depend of your current view(target and zoomlevel of view),
So it isn't really sure what "select" will find.
You should use ZOOM to make sure the objects are near enough (and if SELECTIONOFFSCREEN is off, you can use zoom too for make sure the area is visible. Or set SELECTIONOFFSCREEN on)

Without command, selectionset can create by using ssget and ssadd.

Re: Basic autolisp question

john.uhden — Mon, 11 Jun 2018 23:39:23 GMT

It depends on what types the pairs are made of so that suitable responses are fed to the command invoked.

But, for example, if the pairs are all reals, as in ((X1 Y1)(X2 Y2)... (Xn Yn)), then.

(command "_.line")
(mapcar 'command pairs)
(command "")
OR,
(command "_.line")
(mapcar 'command (append pairs '("")))

Of course one must beware of running object snaps that might make any supplied point end up at the end or middle of other thingies. Adding "_non" before each point is one way but slightly difficult to program, so it might be best to turn off osnaps before the command and turn them back on after.

Here's one way...

Before:
(setvar "osmode" (logior (getvar "osmode") 16384))
After:
(setvar "osmode" (boole 2 (getvar "osmode") 16384))

I hope I don't have them backwards.

Re: Basic autolisp question

Anonymous — Tue, 12 Jun 2018 10:43:00 GMT

I normally use

(setq oldsnap (getvar 'osmode))
(setvar 'osmode 0)
.....
...
(setvar 'osmode oldsnap)

Re: Basic autolisp question

cadffm — Tue, 12 Jun 2018 11:36:25 GMT

That deselect all osnap settings, if you don't use a error function for reset osnaps, the user will lost his osmode setting.

Osnaps turning off like john shows it is much better in this case.

(Or the real well method for that, command input without osnaps, set osnapcoord to 1)

Re: Basic autolisp question

john.uhden — Tue, 12 Jun 2018 23:24:12 GMT

Sheesh. I never even knew that [osnapcoord] existed. But there it is, even in 2002. But the help speaks only of keyboard entry. What about points computed in AutoLisp or read from a file? I don't think I ever type in coordinates. What about if you point to the direction and enter a distance?

Re: Basic autolisp question

cadffm — Wed, 13 Jun 2018 01:20:02 GMT

Look at options/user preferences upper right corner.

Every time when you give input for coordinates..
No matter how.
Mouse direction and length
,30
Mouseclick
Every click or input for a pickpoint will be as result a coordinate information for acad.
In some situation acad is asking for a object, you can click them or select it by 200,400 - in first line both are coordinate information for acad,
At the same time acad calculate the coordinate point by the current osnap one or more are active.

Coordinates 1 is default.
Whenever you using the keyboard for input, acad ignore the running osnap(osmode).
Thats good, because you never want a osnap point when you working with the keyboard, or you will use the temporary snap explicit.
Ps: osnapcoord set to 0 can be a really bad thing(users who playing in options and change this setting to 0)
Unexpected results welcome.

But osnapcoord(1) is only for ignoring running osnaps by keyboard input from users,
it is not for automation inputs like macro script (commands or sendcommand from other APIs)
When you needed osnaps without input by user? Not so often..
Osnapcoords 2 includes coordinate inputs from automations (control commands with lisp,scr,macros and so on)

Value 2 should be the default, but it isn't from adesk.
1 or 2, for normal user work it is the same.
But you knowing about millions of lisp snippeds and dirty macro/scripts/lisps and blind using users.
Value 2 should be default and protects users for some gray hairs, but it isn't by adesk.

Re: Basic autolisp question

cadffm — Thu, 14 Jun 2018 00:47:17 GMT

Last answer yesterday it looks like i was very tired.
Of course it should read
Default 2 (only keyboard)
My opinion is it should be 1 (keyboard and automation)
i am sorry for confusion.