Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Can anyone tell me what is wrong with my LISP routine? I have been banging my head trying to find the error, but cant. The error I am getting is :"error: AutoCAD variable setting rejected: "osmode" nil". The error occurs when CLR is initiated.
In the CLR routine, where are you setting a value for the variable OSM,
before you attempt to use the variable?
All the functions you posted look like subroutines. Where is the command
function?
--
R. Robert Bell
wrote in message news:5389226@discussion.autodesk.com...
Can anyone tell me what is wrong with my LISP routine? I have been banging
my head trying to find the error, but cant. The error I am getting is
:"error: AutoCAD variable setting rejected: "osmode" nil". The error occurs
when CLR is initiated.
They are contained in the menu file. I have created image menus, and each of these subcommands are to be used within the image menu definitions. For example, this menu item inserts a detail bubble with attributes as well as a detail line at the same insertion point as the detail bubble. I wanted it to turn off osnaps, set the correct layer, insert the blocks, then reset the osnap and layer settings.
It sounds a lot like the variable for the current Osnap modes wasn't set
somehow, before it was called for to reset OSMODE. That would make that
variable come back as nil, but it won't let you set OSMODE to nil -- only
numerical values (if Osnap is off, that's zero rather than nil).
Make sure the subroutine that sets that variable has been run before this
one that's trying to use it.
In any of the menu definitions, the GCL and OFF routines are run first, which is supposed to turn off osnaps (osnaps are typically on at this point), then it runs the series of commands, then runs CLR, which turns the osnaps back on. I tried what MiD-AwE wrote, and I still get the same error. Im not sure what Im doing wrong, do you have any ideas on what I can change to eliminate this error?
But if they're using (getvar) to set them from the System Variables they're
now trying to set back, I'm having a hard time figuring out how they could
be illegitimate values. Unless something else is messing with them in
between...?
--
Kent Cooper
"Allen Johnson" wrote...
You need to make sure OSM and CLY are set to a legitimate value. Like:
I'm guessing that you are possibly using a function name as a global variable name elsewhere in you code (anywhere in your acad.lsp, acaddoc.lsp, etc.).
First off, you should set Globals with UNIQUE naming Like *OSM* as the help files suggest. This is because if you happen to have a function named CLR and you attempt to use CLR as a variable name you may get an error. I say "you may" but chances are you will.
I have some similar functions that I wrote for the same purpose, I imagine. If you like, try them: Use (GV) at the beginning of your code to Get Variables, use (SV) at the end of your code to reSet Variables.
[code]
(DEFUN GV () ;GET VARS
(SETQ *CMD* (GETVAR "CMDECHO")
*OSM* (GETVAR "OSMODE")
*OTM* (GETVAR "ORTHOMODE")
*CLY* (GETVAR "CLAYER")
*CLR* (GETVAR "CECOLOR")
*SNA* (GETVAR "SNAPANG")
*TXS* (GETVAR "TEXTSTYLE")
*ATD* (GETVAR "ATTDIA")
*ATR* (GETVAR "ATTREQ")
*PLRM* (GETVAR "POLARMODE")
*SNM* (GETVAR "SNAPMODE")
*PEA* (GETVAR "PEDITACCEPT")
*PLW* (GETVAR "PLINEWID")
*PLG* (GETVAR "PLINEGEN")
*DMS* (GETVAR "DIMSTYLE")
)
(PRINC)
)
In the context of a menu macro, most of those subroutines are unneeded. I
*wouldn't* advise turning of OSnaps in the macro (the user might want them),
and there is no need for the (pt) routine. Running OSnaps can be overridden
at a prompt using the "NONe" override.
So that leaves only the CLayer save/restore as useful subrs.
wrote in message news:5389247@discussion.autodesk.com...
They are contained in the menu file. I have created image menus, and each
of these subcommands are to be used within the image menu definitions. For
example, this menu item inserts a detail bubble with attributes as well as a
detail line at the same insertion point as the detail bubble. I wanted it
to turn off osnaps, set the correct layer, insert the blocks, then reset the
osnap and layer settings.
Sometimes in my quest for perfection, I make simple things more difficult than they have to be 😉 I never knew the @ symbol referenced the last point. I learn something new every day. And I never thought to simply use the _non command. Thank you for that.
Now I get this error:
(i:SetCL) ; error: AutoCAD variable setting rejected: "CLayer" nil
Does it have anything to do with the nil at the end of the setq string?
wrote in message news:5389411@discussion.autodesk.com...
Sometimes in my quest for perfection, I make simple things more difficult
than they have to be 😉 I never knew the @ symbol referenced the last
point. I learn something new every day. And I never thought to simply use
the _non command. Thank you for that.
Now I get this error:
(i:SetCL) ; error: AutoCAD variable setting rejected: "CLayer" nil
Does it have anything to do with the nil at the end of the setq string?
All the PRINC changed was that it stopped the "error: AutoCAD variable setting rejected: "CLayer" nil" error from showing, now it only returns: (i:SetCL), but still does not reset the layer.
All the PRINC changed was that it stopped the "error: AutoCAD variable
setting rejected: "CLayer" nil" error from showing, now it only returns:
(i:SetCL), but still does not reset the layer.
