identifying nested references

[clbond]

when a dwg has references which also contain references, and those sub-references are listed in the reference dialog box, is there any way to identify which nested reference is attached to which regular reference?

[BlackBox]

Welcome to AUIG! :beer:

Consider the XOPEN (http://exchange.autodesk.com/autocad/enu/online-help/browse#WS1a9193826455f5ff-6ab24494122f0f3d6b87c17.htm) Command... The Open Reference Files dialog should correctly show any nested external references prior to completion of the command:

http://exchange.autodesk.com/autocad/enu/online-help/ACD/2012/ENU/attachments/dlg_open_references_files.png

[clbond]

Well, I don't get the dialog box, just listings on the command line, but I can F2 to follow through. Thanks! (And I couldn't locate the xopen in the SYSVDLG to change that setting.) I've been a member of AUGI since it was NAAUG; hard to believe that I never posted anything before....

[cadtag]

the CLASSICXREF command allows one to toggle between the flat view, and a tree view which will display nesting structure and depth

[BlackBox]

the CLASSICXREF command allows one to toggle between the flat view, and a tree view which will display nesting structure and depth

The ClassicXref tree view is useful, but is there a system variable that allows for the tree view to persist?

[cadtag]

not AFAIK..... guess it wasn't 'cool' enough

[clbond]

AHH! and oooh!

Thanks, gurus!

Note: there was also something goofy going on with no-longer existant files with locked layers that had to be unlocked before I could detach...hmmm

[irneb]

The non-classic treeview does persist from what you had displayed previously:
88499

[cadtag]

Thanks for pointing that out. I'd completely missed those two icons on the top right -- :Oops:

[BlackBox]

Thanks for pointing that out. I'd completely missed those two icons on the top right -- :Oops:

Agreed, thanks Irneb... I actually have my XR alias set to use ClassicXref still, as the XREF Palette does not support multiple select in kind (which it should).

[irneb]

Agreed, thanks Irneb... I actually have my XR alias set to use ClassicXref still, as the XREF Palette does not support multiple select in kind (which it should).Yes understood, the major reason for me using the ClassicXRef command is when changing xrefs between overlay & attachment (in classic it's a double click, in new it's select, scroll, pick drop-down, select option ...).

This was yet one more of those "awesome" additions adesk are so (in)famous for. In anyone else's dictionary it reads: "Feature reduction". But ADesk thinks they are "upgrades".

[BlackBox]

Yes understood, the major reason for me using the ClassicXRef command is when changing xrefs between overlay & attachment (in classic it's a double click, in new it's select, scroll, pick drop-down, select option ...).

This was yet one more of those "awesome" additions adesk are so (in)famous for. In anyone else's dictionary it reads: "Feature reduction". But ADesk thinks they are "upgrades".

No, I agree... The utter irony in this specific example (for anyone adept at .NET development, and form work), is that the ClassicXref Form Designer code source, could (perhaps should?) have been dropped into the User Control that is presently being hosted within the AutoCAD Tool Palette that is displayed with the OOTB XREF Command.

They're would be some obvious need to perform some code maintenance on the code-behind (the source code that is executed when a button is pressed, which is really a Click Event, etc.), but still... Far less work (IMO) than creating an all new, flashy would-be replacement for the ClassicXref dialog. Just saying.

[cadtag]

Sure, but history suggests that a typical adesk developer coming onto a project would rather re-invent a round wheel using the latest/greatest than fix or update something that's been around multiple versions. It seems to be a common theme at san rafael. eg Write QuickCalc and embed it into the properties palette, instead of putting a gui front onto CALC, creating new Group functionality without fixing/updating the old Group dialog, not enabling an 'overlay' option fior image/pdf/dwf attachments. Instead of fixing problems with tool palettes, go to a Ribbon. Pretty much an expansion of the NIH syndrome....

Personally, I suspect it's staff turn-over. the folk who started and did initial development on things like ADC and SSM moved on/elsewhere, and the replacements don't get the point of the tool, don't like it, or can't follow the old documentation.

[irneb]

... moved on/elsewhere, and the replacements don't get the point of the tool, don't like it, or can't follow the old documentation.If this is true, then all I can say to them is "tough", ACad is not supposed to be created for you programmers. If I can't catch-up on a project half-way through after the previous guy left the company, then I'm FIRED! So should THEY!


These things are like infestations throughout adesk's products. Huge quantities of extra code either doing useless stuff, or (worse) removing useful features. Revit is actually more infected by this VIRUS: E.g. Why are you unable to join a column to a beam so their joint is seamless (R.C. column & beam that is), while the column may be joined to other stuff (like brickwork)? That actually needed extra coding to remove something which should have been there.