Request for AutoLISP
A couple of things I notice:
Yes, (vl-load-com) may be needed to get the (vl...) functions in [once per editing session, but it's often built into routines that will need it if they contain the first call to any of them].
I think this:
(setq x_lay (vla-get-layer obj))
should be this instead:
(setq x_lay (vla-get-layer x_obj))
HOWEVER, the problem with (nentsel) is that it digs down to the lowest level of nesting of whatever you pick on. So if there's a Block nested in another Block in your Xref, and the part of it you pick on was originally drawn on Layer 0, what you will get from that will be Layer 0, not the Layer on which either level of Block was inserted, nor that on which the drawing was Xref'd. And Layer 0 is a strictly on-its-own Layer name, never associated with an Xref in XrefName|0 fashion.
I have a routine that accounts for that -- LayerQuellPick.lsp, available >here<. Look at the setting of the layq variable. If you pick on something that at its lowest level is on Layer 0, it steps up through nesting levels until it hits some other Layer, i.e. the one on which the object "appears."
But I expect you can just use (entsel) for the overall Xref, and pull the portion of its name from what you get there, rather than digging down to nested things.
I still don't get why you're A) picking a nested object to extract the Xref's name from the Layer of that object, when you can just get it from the Xref itself, and B) getting a list of all Layers and stepping through them all, comparing them to the Layer names you're after, when you can just apply options to the ones you want. Can't it be as simple as this?
(defun C:WHATEVER (/ xrs xrn)
(if
(and
(setq xrs (entsel "\nSelect XREF to process is Layers: "))
(setq xrn (cdr (assoc 2 (entget (car xrs))))); name from entity data
(assoc 1 (tblsearch "block" xrn)); it's an Xref
); and
(command "_.layer" ; then
"_color" 152
(strcat xrn "|CS-BLDG-OTLN," xrn "|CS-BLDG-EAVE")
"_color" 190
(strcat xrn "|CS-BLDG-ANNO," xrn "|CS-BLDG-CONC")
"_color" 156
(strcat xrn "|CS-BLDG," xrn "|CS-BLDG-DOOR," xrn "|CS-BLDG-WIND")
"_plot" "_no"
(strcat xrn "|CS-BLDG-DWNS," xrn "|CS-BLDG-NUM~")
"_freeze"
(strcat xrn "|CS-BLDG-COLU," xrn "|CS-BLDG-STEP")
"" ; close Layer command
); command
); if
(princ)
); defun
@SnickerinTurtles wrote:
.... Because it has to check each layer to see if they match. ....
Good for you for making the effort to learn more. [I don't have books to suggest, but a Search in this Forum for books, tutorials, learning, and related terms will give you more than you can ever look into.]
The sentence quoted above still concerns me. It is certainly not necessary to check each Layer! The Layer command will accept the Layer names of whatever Layers you want to do something to, and all other Layers can be ignored. Pulling a list of all Layer names, and stepping through it, means that you are checking whether Layer "0" is a relevant nested Layer in the subject Xref, and whether "DEFPOINTS" is, and whether "Peter" and "Paul" and "Mary" are, including whether all Layers that are not even nested in Xref's are. That's a heck of a lot of checking Layers that you're not going to do anything to. But given the root drawing name of the Xref, you can put that together with the "pipe"-character connector and only the specific under-Layer names you want, within each option you want applied, and that is all. [That's what my suggestion does -- I hope it actually works, but I didn't set up the situation to try it.] No dealing with irrelevant Layers at all; no pulling of a list of Layers at all. And it won't care if some of them don't exist. And it's not even case-sensitive as (wcmatch)-based checks are.
(setq clr (acad_colordlg 7))
This starts index color dialog and after selection places color number to variable clr. In this case we ask to open dialog with index color 7 selected
(setq clr (acad_truecolordlg 7))
Return color codes to be included in entity definition. Something like:
((62 . 132) (420 . 2997458))
((62 . 142) (420 . 38875) (430 . "PANTONE+ CMYK Uncoated$PANTONE Process Cyan U"))
@grobnik Next time just start a new post
Miljenko Hatlak
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
