Entmaking XDATA

David - What you're doing makes sense to an extent, and
if you're not dependent on an applications that use
inter-object referencing or hang data on extension
dictionaries, then I suppose that there is no damage
done using this approach.

 

Hi David,

If the purpose is to get rid of certain data and recreate the entity, try
this.
;;============
(defun tryme (ent / removelist) ; 'ent' is the entity list returned by
(entget)
(setq removelist '(-1 5 100 330)) ; dxf group codes to remove
(foreach dxfitem
removelist
(while (assoc dxfitem ent)
(setq ent (vl-remove (assoc dxfitem ent) ent))
)
)
(entmake ent)
)
;;============
Just add the dxf group codes to removelist that you don't want to be in the
new entity. But remember essential group codes must present.

Hth,
PG.

 

Then I understood you correctly about the custom objects.

Like making a copy of a ADT object, that perhaps has its own inner methods
and custom commands for cloning an object, instead of using the regular
copy, mirror, etc.

 

I've been burnt on that approach in the past. Trying to out guess what
ADESK will add next is a no win situation. Whereas the basic required
codes have been constant with a few exceptions over the years. The
recent thread on exploding MINSERTS is 1 such example. I still think
ADESK did the biggest screw up in years by not allowing them to be
easily converted back to INSERTs or exploded is a shame. I get more
calls about using them than anything else I do.

I think that are a still a few group 100s that must be included in
entmake calls. That should have been a consistent either you must or
you don't have to. IMO.

-David

 

Good point; don't want you to get burnt again.

<snip>