Change to layer 0 (make layer 0 current)
Is Layer 0 Frozen? That possibility may be the only reason a REGEN might be needed. If so, it can't be made current. Try adding a Thawing of it first.
The hyphen prefix isn't needed when inside an AutoLisp (command) function, where the command-line version is the standard, not the dialog box.
If you use the Layer command's Set option, it will turn it on if it's off, so you don't need to turn it on. Besides, there's no point in the Make option to set it current, since that Layer can never be Purged, so it must always exist in the drawing already.
Could you have a differently-defined LAYER command? Possibly if you use an overlay, not just "vanilla" AutoCAD. Using the period prefix will force use of the native command. [And I always include the underscore so the same command can be used in other-than-English versions -- users of this Forum are from all over the world.]
The LAYER and REGEN commands can be in the same (command) function together.
(defun C:L0 () (command "_.layer" "_thaw" "0" "_set" "0" "" "_.regen")) ;;Change to layer 0 and regen
@Brock_Olly wrote:
... here's what GPT has to say.. ....
Another demonstration of a variety of things it doesn't know [yet].
It suggests checking whether Layer 0 exists, but that is pointless -- it always exists, because it cannot be Purged, nor Renamed.
It does not account for the possibility that Layer 0 could be Frozen, in which case it cannot be set current [by either method below].
It suggests replacing (GRAPHSCR) with (command "GRAPHSCR"), which will do no good, because it doesn't know that (GRAPHSCR) is a legitimate AutoLisp function, as well as a command.
It suggests using (setvar 'clayer "0") to make it current. That will not turn the Layer on if it's off, the way the Set option in a Layer command will.
I've pointed out these things to it at that link, and it has adjusted its recommendations. [EDIT: Well, it responded and adjusted when I "spoke" to it about these things, but the changes didn't stick -- I just picked the link again and it's the original with all the flaws.]
U0, U1 & U2 work fine in my AutoCAD 2020...
What happens when you copy & paste each of the defun lines into your command prompt and then run it like the way I did below?
I also notice you have these 2 lines of code which represent the same sequence of commands:
(defun C:SHE () (command "SHADEMODE" "O")) ;; 2D WIREFRAME DISPLAY
(defun C:SH () (command "SHADEMODE" "O")) ;; 2D WIREFRAME DISPLAYBut SH command is set aside by AutoCAD in acad.pgp to run an OS command:
So I would remove the following from your lisp code:
(defun C:SH () (command "SHADEMODE" "O")) ;; 2D WIREFRAME DISPLAY
you are welcome and I would not bother with VLIDE but jump right into what Autodesk now supports as VS Code:
https://help.autodesk.com/view/ACDLT/2024/ENU/?guid=GUID-7BE00235-5D40-4789-9E34-D57685E83875
Also install the following VS Code Extensions:
@stev98312 wrote:
Will this work for you?
; put pre-selected object(s) [if any] on Layer 0, otherwise set current Layer to 0
That's my code, from >here<, except that I [coincidentally] used the same command name L0 that this Topic's OP uses. I thought of posting it as part of my earlier suggestion, but the changing of objects to that Layer didn't seem part of what they want to do, so I included only its no-pre-selection 'else' argument.
When using Notepad++ I take it you have the LISP option ticked on under Language, when you place the mouse say at a starting bracket it should turn red scrolling down should reveal the matching closing bracket, I always check the starting Defun bracket and end of defun if no match go looking.
The other thing is you can load under Plugins the "ActiveX" plugin it allows you to run the lisp code in the editor.
