Topic: a deliberate faux pas....honestly

[Big G]

cad crashed...i opened the xref autosave (not realising that the autosave was from last week) and saved over my drawing (containing todays work).....BUT by some miracle means i managed to open another drawing that crashed too and has the 'correct' xref file....

question.
The xref is still pathed to the (saved over) xref file but has the correct data...is there a way i can explode or export or generally split the (correct) xref, subsequently  ending up with it not being xref'd into the dwg?

clear as mud??!!??  :ugly:

to summise...
cad crashed...opened 2 files which were open before the crash and managed to overwrite the xref with last weeks autosave...meanwhile in the other drawing....the xref has read from the file before i overwrote it..and i need to use that xref again...is there a way i can get it back.....
the .bak and .sv$ are usless.....

[Dinosaur]

I would think that if the xref is correct in that one file, it exists intact somewhere in the search path of that file.  Open the file with the good xref and check what file is being referenced.  You should be able to open and save that file for use with the other file as well.

[Big G]

dino...Ive saved over the xref with last weeks one....the open drawing only has the correct xref as i havent updated it yet.....(which is the one prior to me overwriting it)

[Dinosaur]

bad news that . . . right now that drawing only exists in you computer's memory.  I think you might still be able to bind the xref to the drawing and save the whole thing as a new file, but it will be quite a mess to work with.

[Big G]

already been tryin that dino....it wants me to update it before it will let me bind it....even a ctrl-c paste into new drawing repaths it to the wrong xref....dagnammit!!
just wondering if anyone had a 'burst' xref routine? to explode the xref'd entities back into lines/arcs etc...??

[MP]

Hang on ... I'll try to code something up ...

[Big G]

bork bork bork!! eets ze sveedish zhef!!

[Dinosaur]

it may not make any difference at all, but you could rename that referenced file (might not be a bad idea anyway or at least copy it somewhere) and see if AutoCAD still demands an update

[MP]

<code deleted>

[Big G]

as wayne and garth once said "We're not worthy!!!"

awesome job...one xref redrawn and ones derriere saved for another day 

[MP]

Glad to hear you were able to recover the xref data. That code has now been retired. Cheers.

[Bob Wahr]

A wise man once said

Separate your ego from your code. Your code is not you <snip>. I'm about to disappoint you but we don't like you because of your code. We like you because you share your code, your expertise, your perspective, your triumphs and your failures, your life.

If you happen to post some code and it's less than perfect oh well, we don't think any less of you as a person. More importantly, letting less than perfect posts exist for perpetuity demonstrates humility as well as personal growth - look how well I code now compared to a year ago, woot.

Are these bad things?

[MP]

I deleted that code because it could be used incorrectly, I have zero interest in supporting it or (added) discussing it.

I should have sent the code to the poster privately.

I'll not make that mistake again.

[Bob Wahr]

just sayin'

[Josh Nieman]

just sayin'

Glad someone else said what I was thinkin'

[craigr]

Just Curious....

How could it be used 'incorrectly'?

craigr

[Josh Nieman]

Just Curious....

How could it be used 'incorrectly'?

craigr

Kinda like how someone could hit their thumb with a hammer... so I guess we should now stop selling hammers.

[Bob Wahr]

Actually there should be a self-appointed committee of one who decides who can and can't sell hammers.  Not everyone is able to decide if their hammers should be available to the public or not.