Autosave disappearing after closing drawing while in block editor

[SilverRey]

I recently closed my drawing while still in block editor (those x's are way too close to each other), went to get my autosave and it was gone. Has anyone else run across this? This has happened to me on separate occasions now.

The backup files for the autosave remains, but the autosave file itself is gone. And I have the autosave set to 5 min, so there should always be something there....

[Mamma Jamma]

I recently closed my drawing while still in block editor (those x's are way too close to each other), went to get my autosave and it was gone. Has anyone else run across this? This has happened to me on separate occasions now.

The backup files for the autosave remains, but the autosave file itself is gone. And I have the autosave set to 5 min, so there should always be something there....

If you close out of AutoCAD intentionally (hitting the "X" is considered intentional) the Autosave will go away. It's only retained in the case of a crash.
I have, on occasion, had reason to crash myself out, and renaming my Autosave prior to killing Acad has been a savior. But, sorry, the nature of the beast is that it won't be retained in the case of an elegant exit.
Bottom line, you can't use Autosave as a replacement for Qsave and a BAK file.

[cadtag]

I really need to add that to the 'paper cuts' thread. it _ought_ to be impossible to exit the parent application (Acad) while in the child application (Bedit), Hitting either X for close should either close bedit first and prompt after that to save, or only close bedit. It's a common error compounded by a design flaw

[CADastrophe]

I really need to add that to the 'paper cuts' thread. it _ought_ to be impossible to exit the parent application (Acad) while in the child application (Bedit), Hitting either X for close should either close bedit first and prompt after that to save, or only close bedit. It's a common error compounded by a design flaw

I agree with that thought 100%. Oh, the headaches that's caused here...

[BlackBox]

I can understand this... But you're neglecting the fact that there are Application level Commands, and Document (read Drawing) level Commands, where entity modification represents an instance of the latter.

In the meantime.... Rather than holding one's breath until this is fixed by the product design team(s), using Kean's post here:

Blocking AutoCAD commands from .NET (http://through-the-interface.typepad.com/through_the_interface/2006/10/blocking_autoca.html)

... You could implement a small .NET plug-in framework, which sets a bool typed Field or Property to true when a *BEDIT Command is invoked, and set to false when the *BCLOSE Command is invoked... Whilst said bool typed Field or Property == true, simply veto the QUIT Command.

I'm certain there are other conditions that my simple logic may be overlooking while making this suggestion, but reasonably doable, methinks.

If you really wanted this to be user-defined, you could easily incorporate XML defined settings.

[cadtag]

One of the great things about Acad is that it's possible work around design flaws - one of the terrible things about Acad is that it's possible to work around design flaws :beer:

[arshiel88]

I really need to add that to the 'paper cuts' thread. it _ought_ to be impossible to exit the parent application (Acad) while in the child application (Bedit), Hitting either X for close should either close bedit first and prompt after that to save, or only close bedit. It's a common error compounded by a design flaw

+1 on this. As far as I know, autosave is disabled when reference editing. Ive been working in 3D and using blocks a lot. I used to edit a block for hours mostly via REFEDIT (not sure about BEDIT, probably the same), and when an error occurs while reference editing, there is no autosave. So its not just on an elegant exit there is no autosave.

[gfreddog]

One of the great things about Acad is that it's possible work around design flaws - one of the terrible things about Acad is that it's possible to work around design flaws :beer:

Keeps Cad Managers on our toes... and forced me to start learning LISP...

[BlackBox]

Keeps Cad Managers on our toes... and forced me to start learning LISP...

FWIW... I'm just an (albeit underutilized) entry level CAD Technician, by title.

The mere mention of the phrase "CAD Standards" at my office is akin to blurting profanity in church... They want nothing to do with any sort of efficiency initiative (I've even offered some of my personal time to demonstrate), and I was told flat out that we have a small enough group that inconsistencies aren't really of concern... It's demoralizing, really.

/vent