Topic: Leader Text

[Lee Mac]

How can one tell, using Visual LISP, if Text is associated with a leader?

Thanks in advance,

Lee

[Joe Burke]

Lee,

This seem too simple. Check the Annotation property of the leader object. If it returns an mtext object...

[Lee Mac]

Lee,

This seem too simple. Check the Annotation property of the leader object. If it returns an mtext object...

Sorry Joe, I meant if you don't have the Leader Object, but just the Text/MText object - can you tell if they are connected?

I would normally check for the presence of the reactor in the DXF table, but I see no immediate way to accomplish this in VL

[CAB]

I see no way but to search through all reactors.

[Lee Mac]

I see no way but to search through all reactors.

Oh, I thought there might be an easier way that I was missing 

Thanks anyway guys.

[Crank]

Perhaps:

• First make a selectionset of all leaders
• Now make a list of the 340 dxf-codes (= pointers to the mtext)
• If the entityname of the text is a member of the list then it's associated with a leader

[Lee Mac]

Nice idea Crank, thanks

But I really need to do this with VL, as I'd be using it through ObjectDBX. But, on the topic of testing the text for a leader using dxf, I normally use something like this:

Code: [Select]

(defun isLeaderText (ent)
  (and (assoc 102   (entget ent))
       (setq own    (cdr (assoc 330 (entget ent))))
       (eq "LEADER" (cdr (assoc 0 (entget own))))))

Not sure if that's a good way to do it though 

[T.Willey]

You might be able to still do it that way with ODBX.

[Lee Mac]

You might be able to still do it that way with ODBX.

I'll give it a try

I know that entmod isn't available, but entget might be 

[alanjt]

Nice idea Crank, thanks

But I really need to do this with VL, as I'd be using it through ObjectDBX. But, on the topic of testing the text for a leader using dxf, I normally use something like this:

Code: [Select]

(defun isLeaderText (ent)
  (and (assoc 102   (entget ent))
       (setq own    (cdr (assoc 330 (entget ent))))
       (eq "LEADER" (cdr (assoc 0 (entget own))))))

Not sure if that's a good way to do it though 

In early '08, I wrote a routine that would copy (with option to delete) text objects with the QLeader command and change to the current layer. I used the same method to find and delete the attached leader. It did have a flaw that if the MText object had an associated leader, yet already deleted, an executed entdel on an already deleted leader would recreate it. I never followed through with figuring it out since we switched to Multileaders shortly after and I haven't used it since.

[Lee Mac]

Thanks Alan

[T.Willey]

In early '08, I wrote a routine that would copy (with option to delete) text objects with the QLeader command and change to the current layer. I used the same method to find and delete the attached leader. It did have a flaw that if the MText object had an associated leader, yet already deleted, an executed entdel on an already deleted leader would recreate it. I never followed through with figuring it out since we switched to Multileaders shortly after and I haven't used it since.

Just FYI... you can see if an entity is deleted a couple of ways.  If ' entget ' returns nil, then it has been deleted.  You can also use ' vlax-erased-p ' on an ename or vla-object.

[alanjt]

In early '08, I wrote a routine that would copy (with option to delete) text objects with the QLeader command and change to the current layer. I used the same method to find and delete the attached leader. It did have a flaw that if the MText object had an associated leader, yet already deleted, an executed entdel on an already deleted leader would recreate it. I never followed through with figuring it out since we switched to Multileaders shortly after and I haven't used it since.

Just FYI... you can see if an entity is deleted a couple of ways.  If ' entget ' returns nil, then it has been deleted.  You can also use ' vlax-erased-p ' on an ename or vla-object.

Ahh, good to know. Thanks Tim.