database.insert kills parametric constraints...?

This widget could not be displayed.

database.insert kills parametric constraints...?

Anonymous
Not applicable

Hello, 

 

I'm basically try to boost up the "PASTECLIP". The user does a COPYCLIP or COPYBASE some objects and uses my Plugin for inserting (in another or the same drawing). 

I get the clipboard-dwg as a sideDB, ask user for insertion point, move the objects in the clipboard-dwg, rename all the BTR's of the Modelspace Blockrefs by attaching a GUID (to avoid "ignore" on insert - actually this is the "Boost") and insert the sideDB by calling the "db.Insert(Matrix3d.Identity, edb, True)" where db is the destination Database (current document). All looks fine, except Blocks featuring parametric constrains. These will be gone on insert.....

I did some saving on the db-alternation, and the clipboard-dwg still has these parameters.... 

Sure I could call the command "PASTECLIP" after altering the clipboard-dwg, but since this is not the .net-way I'd like to avoid commandline calls....

 

So the question is, is this really a "bug" in the insert method, or am I missing something here?

May I go with "wblockcloneobjects" instead?

 

BR,

Daniel

0 Likes
Reply
297 Views
0 Replies
Replies (0)