polyline length on leader
@Anonymous wrote:
on mine when i select a line it only lets me choose the one line. and then it ask me to choose a point perpendicular to the line. and the only thing that it is measuring is the length of where the leader starts away from the line
do i need to change some settings or something?
i am using the command test to start using the lisp after i appload it.
What you need to change is the command name you're using. TEST is the command name from the other routine from @Satish_Rajdev. The command name in mine is LTLL [always the part that immediately follows (defun C: in the command-defining code].
Kent Cooper, AIA 
@Anonymous wrote:
the last thing is being able to select the filleted bends and add that into the total measurement if that is possible. and if the text can come at the end of the leader instead of being positioned above the leader. ....
I'm not sure what you mean about the bends. In Message 23 you said they were c[h]amfered, but here you say filleted. If Chamfered, are they not also Lines like the rest, that you can select along with the rest? If filleted, Arcs would need to be added to the selection filter, and a different method would be needed to get their length [Arcs don't have a 'Length VLA Property as Lines do] -- not difficult, but I'll wait to hear whether Arcs are involved.
Where the text lies in relation to the Leader line element is a function of the DimStyle of the Leader -- modify that to place the text where you want it [or make a separate Style for these, if you don't want to affect Dimensions that use that Style].
Kent Cooper, AIA
Accepted solution
So, Filleted rather than Chamfered. Try the attached [note that I added a letter to both the file name and the command name ].
BUT if these are always contiguous-at-their-ends series of Lines and Arcs [or all Lines if Chamfered], I would strongly recommend that you make them as Polylines instead of all those separate pieces! It would use less memory. You can do line segments for the "base" route [or, if you have Lines already, join them together into a Polyline with either JOIN or PEDIT's Join option], and then you can Fillet or Chamfer all the bends at once, using the Polyline option in either command. Not to mention that it would involve selection of only one object in a routine to do this labeling, and the determination of its length would be direct and immediate, not by a calculation involving stepping through separate objects and adding up their lengths.
Kent Cooper, AIA
Accepted solution
@Anonymous wrote:
how do i get the text to dome at the end of the leader line instead of on top of it? ....
DIMSTYLE command [just plain D is the default alias for it]; pick the applicable Style name; Modify...; Text tab; Text placement area.
Kent Cooper, AIA
Accepted solution
@Anonymous wrote:
1. .... is it possible to use a spline type leader with multiple points ....
2. can we round up the measurement up to the next foot if there are inches (ex 1'-1 1/2" = 2' or 5'-7" = 6'). ....
The attached is close. The one drawback is that after the second point designation in the Leader, you don't see it forming as you pick points, until you end it, then it's drawn in and the text goes in. I'm not sure whether there's a way to get around that, but if I think of anything, I'll be back. I suggest [if you don't already as I do] turning on .BLIPMODE so you can see what points you've picked so far, and you can route it around stuff with a good idea of where it's going. That could be built in, if you like, and turned off at the end if you don't normally use Blips. [I always have them on -- I find they provide very useful information -- but a lot of people hate them, or don't even know about them.]
[EDIT: The description in the second line should also include that it's the rounded-up-to-the-next-foot version.]
Kent Cooper, AIA
@john.uhden wrote:
....
Why not just set the mtext option to none, invoke the leader command, and when it's done pick up the last coordinate and add the mtext. Now it won't be attached, but that's easy to fix.
It seems you can set a no-annotation option in a way that "sticks" for MultiLeaders and for Qleaders, but apparently not for "basic" Leaders [at least I haven't found the way] -- it has to be called for within the command every time as an option after getting to the end of the leader part, so that doesn't help. But if the routine switched over to using a MultiLeader to get that possibility, then by completing it with no annotation and putting that in separately, you wouldn't get the turning of the tail end of the leader part to "aim" at the text, and you would need to save defining points to do calculations based on [presumably] the last two of them to decide which way to go from the last one for the text insertion point and what its justification should be. BUT if those are worth working into it, given the task at hand, in one way I like the idea of independent Text, as a "plain" Text object, because Mtext is really overkill for just an integer with a foot-mark after it.
Kent Cooper, AIA