@philsogood wrote:
..... could it be possible to modify the lisp in order to select items instead of converting all objects in the file?
If you're talking about the accepted-solution routine in Message 5, you should be able to do that by simply removing the "_X" [= find everything] selection mode element:
(if (setq s (ssget '((0 . "SOLID"))))
EDIT: Not quite, after all, at least sometimes. With only that change, this part:
(foreach e (mapcar 'cadr (ssnamex s))
will step through a list that, depending on the way the Solids were selected, may contain items other than only entity names of Solids, that relate to the selection method(s). Later I'll try posting something to have it process only the entity names, if someone doesn't beat me to it.
Further EDIT: I notice that some suggestions [including the accepted one] involve first converting the Solids to Polylines, and then Hatching the resulting Polylines. That's a waste -- the Hatches can be drawn directly from the Solids' information, without the middleman. I worked on an approach that does that, and does not have the list problem, and works in any UCS, and prevents selection of Solids on locked Layers, and has an option to retain or delete the Solids, and so on, but questions arise:
Would one want to convert all Solids to Hatches always in the SOLID pattern [if the only purpose is to change the object type but not the appearance], or some other always pattern, or have the option to specify the pattern name?
Would one want the option of a Hatch of lines [not SOLID] over retained Solids, contrasting in color and maybe on different Layers, or should the Hatch always get all properties of the Solid [which would make the Hatch invisible if Solids are retained]?
If contrasting, should that be done by keeping the Solid behind the Hatch, or using a background color in the Hatch itself?
If overlaying like that, should pulling the Hatch to the front in draw order be built in?
Kent Cooper, AIA