Topic: Document "xxx.dwg" has a command in progress.

[mohnston]

I have a .NET app that shows a modeless dialog which is a customized print application.
It works fine except when I try to use the "qsave" command on the drawing after plotting or previewing it.
I get a message at the command line:
Document "xxx.dwg" has a command in progress.

Other commands such as Line, Copy, Move etc. work fine. Even the "Save" command works.

I've searched and read every post I could find on this subject including some in Russian (which may have lost something in the translation to English).

Is there some way to tell the Document that it doesn't have a command in progress?
I don't want to "SendCommand" since the only command that seems to shake the document free is "Save". I don't think it's good manners to save a drawing without the users permission. It's also kind of rude to make them save the drawing when all they did was print it.

Any help?

[Kerry]

That sounds weird !

I have no ideas.

.. so this is redundant I 'spose , except to let you know that someone read the post and cares.

[uncoolperson]

i was told to do something like this so i wouldn't have a problem like you describe... as far as what IsQuiescent is/does.... no idea other http://dictionary.reference.com/browse/Quiescent

Code: [Select]

            AutoCAD.AcadApplicationClass blah = new AutoCAD.AcadApplicationClass();
                AcadState oState = blah.GetAcadState();
                while (!oState.IsQuiescent)
                {
                }[/s]

I read too fast.... i was having the same issue... gave up on not saving, and since i'm the only one to use my big happy batch program i just place a copy of the directory to be printed on my computer, screw with it (usually print) then get rid of it.... my network sucks so this is a better idea even for changing something in the drawing.

[Kerry]

The  oState.IsQuiescent 'Gets true if there is no command, LISP script, or ARX command active; otherwise, it gets false.'

ie like the CMDACTIVE getvar ..

.. it has no .set option ie it's read only.

[Kerry]

UCP, good to see you posting in the NET topics! 

[uncoolperson]

UCP, good to see you posting in the NET topics! 

I'll make problems, you fix em..... deal?

[Kerry]

UCP, good to see you posting in the NET topics! 

I'll make problems, you fix em..... deal?

I promise 

[mohnston]

I had already tried "IsQuiescent".
I doesn't work in this situation. It isn't a matter of syncronicity. (POLICE!)
IsQuiescent never gets true.
Somehow the state of the active document is misreported.

[uncoolperson]

command line, as in the one in autocad... if not continue reading, else... i don't know yet.

blah being AutoCAD.AcadApplicationClass from above


have you tried

Code: [Select]

                blah.Visible = true;, to show what autocad is saying... my problem was i couldn't get it to not complain about saving the document.

[Bryco]

I've had that problem in regular cad (cad2000)

Document "xxx.dwg" has a command in progress

and never figured out what caused it. It seemed to happen in dwgs with layer and spatial indexing, or 3d but I never figured it out. I seem to remember Hit/Retry was an option.
I've also heard that acad2006 and 7 have some issues with printers. We just bought a new copier/printer and it ended up using/leaking  so much resourses the undo command , pljoin and a couple of others were taking forever. Looking at the task manager cad was using double what it normally was. It may be worth looking at your mem usage.

[Big G]

we use a few "add-on" packages here and i get this quite a bit too.....the only fix i have found is to type "EXIT" and when it asks you to save CANCEL it....qsave will work fine then?

as to what causes it.....no ideas!

[Glenn R]

You said you have a modeless dialog...are you locking the document when you do your mojo...if so, are you UNLOCKING it afterward...

From memory, IsQuescient is for out of process communication (ie COM controllers)......

Cheers,
Glenn.

[Kerry]

You said you have a modeless dialog...are you locking the document when you do your mojo...if so, are you UNLOCKING it afterward...

From memory, IsQuescient is for out of process communication (ie COM controllers)......

Cheers,
Glenn.

Hi Glenn, I was going to suggest dockumentLocking, but the ability to make changes to the DB [ commands such as Line, Copy, Move etc. ] caused to to back off the idea.  .... but you may be correct anyway

[Alexander Rivilis]

The same situation: http://www.autocad.ru/cgi-bin/f1/board.cgi?t=32048VX (sorry but in Russian). UNLOCKING document before save it must help you.

[mohnston]

Alexander, the solution you point to is the one I referred to in my original post. I tried running the posts through Googles translator but only understood about half.

I do lock the document at the beginning of the function.

Code: [Select]

Document ThisDrawing = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
ThisDrawing.LockDocument();
Then at the end of the function.

Code: [Select]

ThisDrawing.LockDocument(DocumentLockMode.NotLocked, string.Empty, string.Empty, false);

I have also tried this at the beginning:

Code: [Select]

Document ThisDrawing = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
DocumentLock dLock = ThisDrawing.LockDocument();
And this at the end:

Code: [Select]

dLock.Dispose();

I guess this question is now "How do you UnLock a Locked document?"

[Draftek]

I've had the same problem with different types of apps.

When we ran a command from a toolPalette.
When the command was static and running in MDI
when a variable to hold something related to the database was static.

Me thinks some memory alocation related to the current document is not being disposed.

If you get that unlock document thingy to work, I sure would like to see it.

Thanks.

[Bobby C. Jones]

I guess this question is now "How do you UnLock a Locked document?"

In 2007 you dispose of the lock, like your code shows.  In '06 it was slightly different, but I don't recall the process off the top of my head.

[mohnston]

I have also tried this at the beginning:

Code: [Select]

Document ThisDrawing = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
DocumentLock dLock = ThisDrawing.LockDocument();
And this at the end:

Code: [Select]

dLock.Dispose();


That method worked fine once I moved the Dispose closer to the Lock.
I ended up Disposing the lock immediately after making the changes I wanted to the database.

[Chuck Gabriel]

Alexander, the solution you point to is the one I referred to in my original post. I tried running the posts through Googles translator but only understood about half.

I do lock the document at the beginning of the function.

Code: [Select]

Document ThisDrawing = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
ThisDrawing.LockDocument();
Then at the end of the function.

Code: [Select]

ThisDrawing.LockDocument(DocumentLockMode.NotLocked, string.Empty, string.Empty, false);

I have also tried this at the beginning:

Code: [Select]

Document ThisDrawing = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
DocumentLock dLock = ThisDrawing.LockDocument();
And this at the end:

Code: [Select]

dLock.Dispose();

I guess this question is now "How do you UnLock a Locked document?"

In unmanaged ObjectARX, it would unlock when your dLock variable went out of scope.  I'm not sure if the managed version uses the same paradigm, though.

[Kerry]

LockDocument is covered in the Labs

.. Lab 6 I think.

[Kerry]

Yep.

... Notice we keep a copy of the ‘DocumentLock’ object.  In order to unlock the document, we simply dispose DocumentLock object returned on the original lock request.

[Kerry]

.........
In unmanaged ObjectARX, it would unlock when your dLock variable went out of scope.  I'm not sure if the managed version uses the same paradigm, though.

This could be tested by stepping through the code in the debugger with a 'locals' window open.
If .Dispose IS needed, it may be an idea to include it in a try/finally block or wrap it in a using block for the DocumentLock.


... interesting topic. I look forward to hearing the results.

[mohnston]

What I posted in #17 solved my problem. Thanks to all.

Some of the frustration (and strangely enough the fun) with programming is that some things don't make sense.
For example, why have a LockDocument but not an UnLockDocument? "Dispose" certainly isn't intuitive even in the context of C# programming.
And why is it you create a DocumentLock object by calling LockDocument? Shouldn't it be ThisDrawing.DocumentLock()?

And if we are stuck with LockDocument why not make it a property? LockDocument(bool LockIt).
Then we can just call it:
ThisDrawing.LockDocument(true);
// do my stuff here
ThisDrawing.LockDocument(false);

 :realmad: :ugly:

Ok, I feel better now.

[Glenn R]

This is typically how I do it in C#:

Code: [Select]

Document doc = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
using (DocumentLock docLocker = doc.LockDocument())
{
    // Do your mojo here
}// using ends and 'docLocker' goes out of scope and is automagically 'disposed' of

Cheers,
Glenn.

[MickD]

'Dispose' is an OOP paradigm that saves some typing such as 'UnlockDoc' for example, in Dispose (the destructor of your class) is where you put your clean up code.
Dispose should be called when the class goes out of scope but I have noticed that in .net you still have to call it occasionally. It's probably something to do with garbage collection, sometimes objects can hang around until the gc'r cleans them up which when mixing managed/unmanaged (i.e. wrappers) may be leaving objects 'open' which is causing the trouble, only a guess though.

[Kerry]

And why is it you create a DocumentLock object by calling LockDocument? Shouldn't it be ThisDrawing.DocumentLock()?

......
Ok, I feel better now.

Probably something to do with grammar ... a noun / Verb thing. Types are nouns, methods are verbs .. just a W.A.G.