Leaderboard

Hi hosneyalaa , the post is not for extracting / converting Attributes to Texts , is to avoid this overlay of Attributes / Texts .

hosneyalaa the post is about overlapping text a common problem with field surveys for Civil design when displaying information about a point.

@rlx has pretty much covered it, but I've also posted an explanation here which you may find useful.

don't worry , I can keep myself busy I just made a block with one attribute and put a text in it note-1 , note-2 etc. You select the note you want to delete (you must select the attribute) , it then read the number (in my example the number is 6) and then it deletes note six and renumbers the attributes higher than 6 so note-7 to note-9 will become note-6 to -8. NoNo.dwg

only if your command begins with 'c:' , you can call the command (after loading) on the command line with the name that follows. So when you load 'MyRoutine.lsp' and this routine has a function called 'c:test' you would only have to type test on the command line. In all other cases you have to call the command with parentheses. So when you have a function that is written as (defun test1 ().... you have to start it with (test1). If you have a function (defun LM:Test1 ()... you have to start it with (LM:Test1). The reason why someone uses LM: as prefix would be when your name is Lee Mac. See it as a sort of signature , calling card whatever. So when you write a few brilliant routines for us here on this forum , you could write them as (defun Sheep:Test1 ()... and then someone would have to type (Sheep:Test1) to start your mean lean lsp routine. There are more types of defun , like defun-q and this has to do with how your function will be evaluated (as a list) . This is often used for functions that can modify themselves so very useful for self 'learning' routines. But this is more advanced stuff and there are people that can explain this far more better than me.