Community
@NESSEL wrote:..... each equipment has its own number within the range of 1 to 999, shown with a seperate text . I want to delete the texts which are between 200 to 350. The rest texts will remain the same.
....
I will assume the content of those Text/Mtext entities is only the integer value, without prefix or suffix, etc., and that you mean between 200 and 350 inclusive. If you can get them into a selection set [textss below], you can do something like this:
(repeat (sslength textss)
(setq tent (ssname textss 0))
(if (< 199 (atoi (cdr (assoc 1 (entget tent)))) 351)
(entdel tent)
)
(ssdel tent textss)
)
If you meant between 200 and 350 not including those two numbers, substitute them in place of the 199 and 351.
Kent Cooper, AIA 
@NESSEL wrote:ok, NOW İT WORKS GREAT.... wHAT IF I WANT TO CHANGE THE PROPERTIES OF THESE TEXTS INSTEAD OF DELETING THEM LIKE COLOUR CHANGING?? THANK YOU 🙂
...
(entdel tent)...
Just replace that (entdel tent) line with something like:
(command "_.chprop" tent "" "_color" yourcolor "_linetype" yourlinetype "_layer" yourlayer "")
or whatever property option(s) you need.
Kent Cooper, AIA
Another thing you might consider.... Since you apparently come at this with different numbers, you could make one routine that would ask the User for those numbers, rather than having to make a separate one for every combination.
(defun c:QQLL (/ lo hi textss tent)
....
(initget 5); no Enter, no negative
(setq lo (getint "\nLow end integer (inclusive) to do whatever with: "))
(initget 5)
(setq hi (getint "\nHigh end integer: "))
....
(if (< (1- lo) (atoi (cdr (assoc 1 (entget tent)))) (1+ hi))
....
Or it could be done as a non-C: function with arguments:
(defun QQLL (lo hi / textss tent)
....
(if (< (1- lo) (atoi (cdr (assoc 1 (entget tent)))) (1+ hi))
....
which would be used this way:
(QQLL 210 212)
Kent Cooper, AIA
@NESSEL wrote:THANK YOU VERY VERY MUCH!!! GREAT HELP:) REALLY GREAT:)
You're welcome. One other thing that occurs to me is that if you might be dealing with large numbers of Text objects, you might see a bit of a reduction in processing time if you either:
A. put the "offending" ones into a selection set with (ssadd), and then did the changing of properties on all of them at once, instead of one at a time; or
B. used vla-put-... or perhaps (subst)/(entmod) functions on them to change their properties, instead of CHPROP.
I understand that (command) functions, though they usually require less code, take [very slightly but measurably] longer than other ways of doing most things, which is why A. suggests a way to use one only once. But in B., vla-put-... would require converting each entity to a vla-object, and (subst)/(entmod) would require digging out their entity data, and both would require assigning the properties to them individually. I'm not sure -- that "extra work" might take as much time as the (command) function's overhead.
In any case, if the quantities are relatively small, you'd never notice whatever time difference there might be, so you could leave it alone.
Kent Cooper, AIA
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
