TheSwamp
Code Red => .NET => Topic started by: cadpro on November 04, 2008, 03:49:21 AM
-
Hi,
Can xref be overlayed without detaching it?
Thanks
-
If you detach it, the xref cant be overlayed or attached .. cause it is detached and not linked(referenced) into the drawing.
-
.. and i see that you've posted the same question on autodesk.autocad.customization.dotnet.
will be interesting to see if you get a different answer.
ps;
I haven't checked, but it seems that almost every question you've asked for the last couple of years has been about xrefs ... you should be an expert at them shortly :D
-
:lmao:
-
ps;
I haven't checked, but it seems that almost every question you've asked for the last couple of years has been about xrefs ... you should be an expert at them shortly
I wish I could be! :wink:
-
If you detach it, the xref cant be overlayed or attached .. cause it is detached and not linked(referenced) into the drawing.
All sample codes that I saw throughout the threads do a detach of the same xref before changing it to overlay. But, this doesn't work if the block is xrefed in multiple layouts.
Is there a way to access the xrefmanager to change the xref to overlay?
-
I'd like to know too, it seems like it would be such an easy thing to put in the API.
I would use that in about three different tools I can think of.
-
wait, this is a duplicate thread, let's keep to the other one with all the code.
-
You can try the lisp code here [ http://www.theswamp.org/index.php?topic=25232.0 ]. If it works for you, then you should be able to change it to .Net for your purpose, but it does detach and reattach the xref as the type you want.
-
At a guess, when you change an xref (w/ multiple inserts) from insert to overlay they all change at the same time. So remove all xrefs with that name and reinsert them. Oh I guess you already tried that and it didn't work, silly me.
-
So remove all xrefs with that name and reinsert them.
That is the issue! :ugly:
-
You can try the lisp code here [ http://www.theswamp.org/index.php?topic=25232.0 ]. If it works for you, then you should be able to change it to .Net for your purpose, but it does detach and reattach the xref as the type you want.
That didn't work.
-
You can try the lisp code here [ http://www.theswamp.org/index.php?topic=25232.0 ]. If it works for you, then you should be able to change it to .Net for your purpose, but it does detach and reattach the xref as the type you want.
That didn't work.
Are you working with nested xrefs? If so, then it wasn't tested for that since I don't use them. If not, then maybe you can post the drawing file and xrefs, so that I can test.
-
No nested xrefs. Only title blocks.
-
Why can't you record all the insertion information, then detach and reattach?
You could save a layerstate before and reapply it afterward.
Insertion points and scale factors should not be hard.
-
I got this routine from here, couldnt remember the post it was from.
x2a turns them all to attachments x2o changes them all to overlays
-
detaching is very undesirable, as I have tried that approach of recording the original data, and resetting afterwards.
Its ok on simple stuff, but anything complicated like nested items, or multiple viewports makes it really involved to do. It would be far, far, better to be able to change the attach flag via the API.
-
I agree that it would be swell to be able to change an xref from an attachment to an overlay, but AutoCAD doesn't give that ability at this point in time.
-
what about with dotted pairs in lisp? You used to be able to look at the dotted pairs and change those directly. Someone on vbdesign even came up with a vba routine that changed the dotted pairs.
-
http://www.autodesk.com/techpubs/autocad/dxf/dxf2002.pdf
70 - 8 seems to be overlay.
Block group codes (continued)
100 Subclass marker (AcDbEntity)
8 Layer name
100 Subclass marker (AcDbBlockBegin)
2 Block name
70 Block-type flags (bit coded values, may be combined):
0 = Indicates none of the following flags apply
1 = This is an anonymous block generated by hatching, associative
dimensioning, other internal operations, or an application
2 = This block has non-constant attribute definitions (this bit is not set if
the block has any attribute definitions that are constant, or has no
attribute definitions at all)
4 = This block is an external reference (xref)
8 = This block is an xref overlay
16 = This block is externally dependent
32 = This is a resolved external reference, or dependent of an external
reference (ignored on input)
64 = This definition
-
TWO DXF FILES, ONLY DIFFERENCE WAS XREF TYPE.
OVERLAY
AcDbEntity
8
0
100
AcDbBlockBegin
2
0800200GTB
70
44
10
0.0
20
0.0
30
0.0
3
0800200GTB
1
..\arch\0800200GTB.dwg
0
ENDBLK
ATTACH
AcDbEntity
8
0
100
AcDbBlockBegin
2
0800200GTB
70
36
10
0.0
20
0.0
30
0.0
3
0800200GTB
1
..\arch\0800200GTB.dwg
0
ENDBLK
-
if you change the 36 to 44 or vice versa and open the dxf, the attachement type changes accordingly.
-
Wasn't it SCMDave who was doing that.