Community
Again, I don't work with attributes, but when you insert a block with attributes, doesn't it prompt you for values to put in them [non-constant ones, that is]? If so, you would put that (strcat) function in at the point where that prompt occurs. I'm guessing, but assuming there's only one attribute, and it asks for a value for it right after the block rotation angle, then something like:
{code}
(defun C:BlockVert (/ plobj inc)
(setq
plobj (car (entsel "\nSelect Polyline: "))
inc (if (vlax-curve-isClosed plobj) 1 0)
); end setq
(while (<= inc (vlax-curve-getEndParam plobj))
(command
"_.insert"
"vertex" ; block name
(vlax-curve-getPointAtParam plobj inc)
"" "" "" ; scale factors [1] and rotation [0]
(strcat ; for attribute prompt
"V"
(itoa inc) ; text of parameter number
"-"
(rtos (vlax-curve-getDistAtParam plobj inc) 2 2)
); end strcat
); end command
(setq inc (1+ inc))
); end while
); end defun
{code}
--
Kent Cooper
flopo wrote...
I don't know what you mean by additional prompt to the insertion.
....
Should i ad this to the lisp Blockvert?
{code}
(defun C:BlockVert (/ plobj inc)
(setq
plobj (car (entsel "\nSelect Polyline: "))
inc (if (vlax-curve-isClosed plobj) 1 0)
); end setq
(while (<= inc (vlax-curve-getEndParam plobj))
(command
"_.insert"
"vertex" ; block name
(vlax-curve-getPointAtParam plobj inc)
"" "" "" ; scale factors [1] and rotation [0]
(strcat ; for attribute prompt
"V"
(itoa inc) ; text of parameter number
"-"
(rtos (vlax-curve-getDistAtParam plobj inc) 2 2)
); end strcat
); end command
(setq inc (1+ inc))
); end while
); end defun
{code}
--
Kent Cooper
flopo wrote...
I don't know what you mean by additional prompt to the insertion.
....
Should i ad this to the lisp Blockvert?
Kent Cooper, AIA 
Maybe something like this, if there is only the one attribute [untested]:
{code}
(defun C:MeaPLDist (/ plobj space inc)
(setq
plobj (car (entsel "\nSelect Polyline: "))
space (getdist "\nSpacing of Blocks: ")
inc 1
); end setq
(setvar 'attdia 0)
(while ; as long as next position is not beyond end
(<=
(setq pldist (* inc space))
(vlax-curve-getDistAtParam plobj (vlax-curve-getEndParam plobj))
); end <=
(command
"_.insert"
"blockname"
(vlax-curve-getPointAtDist plobj pldist)
"" "" "" ; scale factors [1] and rotation [0]
(rtos pldist); answer to attribute value prompt
); end command
(setq inc (1+ inc))
); end while
); end defun
{code}
Save and restore the ATTDIA System Variable value if you like, add error handling, etc., etc. Add mode and precision arguments to the (rtos) function if you like [as written, it will just use the current settings], and (strcat) a suffix onto it if needed. Depending on your drawing unit, you may also need to convert if you want it expressed in km.
It would operate like Measure in the sense that it would *not* put one at the beginning of the Polyline. It could be made to by starting the 'inc' value at 0 instead of 1.
--
Kent Cooper
flopo wrote...
....do the same thing like Measure command, but to add at every block inserted at a certain distance ( 1km, or 0.1 km or other distance) the value of the distance?
.... Edited by: Kent1Cooper on Oct 27, 2009 9:46 AM
[corrected a ) to a " as stevor pointed out elsewhere]
{code}
(defun C:MeaPLDist (/ plobj space inc)
(setq
plobj (car (entsel "\nSelect Polyline: "))
space (getdist "\nSpacing of Blocks: ")
inc 1
); end setq
(setvar 'attdia 0)
(while ; as long as next position is not beyond end
(<=
(setq pldist (* inc space))
(vlax-curve-getDistAtParam plobj (vlax-curve-getEndParam plobj))
); end <=
(command
"_.insert"
"blockname"
(vlax-curve-getPointAtDist plobj pldist)
"" "" "" ; scale factors [1] and rotation [0]
(rtos pldist); answer to attribute value prompt
); end command
(setq inc (1+ inc))
); end while
); end defun
{code}
Save and restore the ATTDIA System Variable value if you like, add error handling, etc., etc. Add mode and precision arguments to the (rtos) function if you like [as written, it will just use the current settings], and (strcat) a suffix onto it if needed. Depending on your drawing unit, you may also need to convert if you want it expressed in km.
It would operate like Measure in the sense that it would *not* put one at the beginning of the Polyline. It could be made to by starting the 'inc' value at 0 instead of 1.
--
Kent Cooper
flopo wrote...
....do the same thing like Measure command, but to add at every block inserted at a certain distance ( 1km, or 0.1 km or other distance) the value of the distance?
.... Edited by: Kent1Cooper on Oct 27, 2009 9:46 AM
[corrected a ) to a " as stevor pointed out elsewhere]
Kent Cooper, AIA
If you tried it when I first posted it, it would have had a problem which stevor pointed out. That's been corrected, and all you should need to do is change "blockname" to the name of the actual block you want to use, copy/paste it all into Notepad and save it as MeaPLDist.lsp [or whatever you want to call it], load it and use it. The "if you like" suggestions are optional -- it should work without incorporating any of them.
--
Kent Cooper
--
Kent Cooper
Kent Cooper, AIA
It works for me. But it needs to have no running Object-snap modes in effect -- the attached takes care of that [but you'll still need to change the block name]. I don't really use attributes, so if there is anything about the attribute itself, or some related AutoCAD setting, that could be causing it to not have the distance value put in it [constant value? visibility setting? text size? attribute prompting setting?], I would not be the best person to explore that.
Also, are you currently in the World Coordinate System? If not, that would explain the positioning problem. If that's what's wrong, would you like the routine to compensate for that?
--
Kent Cooper
flopo wrote...
....blocks are inserted but distance values are not inserted in block attribute (all blocks have the same attribute, as initial). Also, blocks are not inserted along the polyline, they are positioned somehow offseted from polyline.....
Also, are you currently in the World Coordinate System? If not, that would explain the positioning problem. If that's what's wrong, would you like the routine to compensate for that?
--
Kent Cooper
flopo wrote...
....blocks are inserted but distance values are not inserted in block attribute (all blocks have the same attribute, as initial). Also, blocks are not inserted along the polyline, they are positioned somehow offseted from polyline.....
Kent Cooper, AIA
It works with whatever the drawing unit settings are, both in asking for the spacing and setting a value to the Attribute. See the UNITS command, and/or the LUNITS, LUPREC, MEASUREMENT, and INSUNITS [and its related] System Variables. This line:
(rtos pldist)
is the one that you would need to adjust if you don't want just a number in current drawing units. For instance, if your drawing unit is a millimeter and you want the Attribute to be expressed in meters, or if your drawing unit is a meter and you want the Attribute to be expressed in kilometers, change that to
(rtos (/ pldist 1000))
Or if you want it to put an "m" on the end for meters,
(strcat (Rtos (/ pldist 1000)) "m")
or "km" instead, etc. It would be possible to ask the User what units they want the Attribute expressed in, if that's what you want to do.
--
Kent Cooper
(rtos pldist)
is the one that you would need to adjust if you don't want just a number in current drawing units. For instance, if your drawing unit is a millimeter and you want the Attribute to be expressed in meters, or if your drawing unit is a meter and you want the Attribute to be expressed in kilometers, change that to
(rtos (/ pldist 1000))
Or if you want it to put an "m" on the end for meters,
(strcat (Rtos (/ pldist 1000)) "m")
or "km" instead, etc. It would be possible to ask the User what units they want the Attribute expressed in, if that's what you want to do.
--
Kent Cooper
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")
