#'Transparent BUG
5 messages in this thread
Hi Jamie,
I seemed to have found a problem using 'SETVAR and some of the (GETxxxx)
functions.
Here's the setup:
Just started an editting session, TEXTEVAL is set to 0. I type in
(GETSTRING) and respond with 'SETVAR. No problem, this works fine.
Now I set TEXTEVAL to 1, type in (GETSTRING) and respond with 'SETVAR.
(GETSTRING) returns "'SETVAR", ok I can live with this.
So now I set TEXTEVAL back to 0 try it again and (GETSTRING) returns
"'SETVAR". OOPS, what happened, strange, this is hard to work with.
(GETSTRING) will also return "'SETVAR" every time after a "Can't re-enter
AutoLisp" error message.
Please let me know what's happening.
Ray Fantasia, MiCAD Systems, Inc.
Ray —
Yep, I'd say that was a bug. AutoLISP should return "'SETVAR" as a
string the first time you use GETSTRING. TEXTEVAL should have no effect
on the value returned by GETSTRING, and in fact, it didn't make a
difference when I tested it.
Thanks, the bug hunters will track it down.
— Brad
..
Brad,
Thanks for the prompt reply. The only other thing that I tend to
find is that the other transparent commands (i.e. 'ZOOM, 'PAN, 'VIEW, etc.)
work correctly whatever the TEXTEVAL setting is. This might be a starting
point for your 'bug fixers'.
Thanks again
Ray Fantasia, MiCAD Systems, Inc.
Well it would seem you have helped us uncover a bug. The condition of which
was not at first evident in your message, but we have the scenario down now.
Problem – When you invoke SETVAR as a command, it will subsequently not work
transparently with lisp. But…
(here is where it gets interesting)…the transparent command will return to
working in the proper manner if you use it with a regular (non lisp) command.
This seems to "reset" it to work properly with AutoLisp.
This problem isn't restricted to SETVAR either, it will do this with all
transparent commands. Also TEXTEVAL plays no part in this except that it was
what lead you to use 'setvar.
Thanks.
Jamie
Thanks Jamie
Talk to you later
Ray Fantasia, MiCAD Systems, Inc.