topic Re: Quiescent state and Command Line in .NET Forum

Quiescent state and Command Line

Anonymous — Sat, 10 Jun 2017 20:01:27 GMT

I am seeing a "document busy" message when using a custom command-line command.

The purpose of the command-line command is to check to see if a newer version of the currently opened drawing is available in other locations.

A check is made, and if a newer version of the document is available, the current document should close, the new version would be downloaded and would overwrite the older version, and the drawing would be reopened and made the active drawing.

It seems like as soon as the command is run the current drawing is marked as busy. I can see that the drawing is marked as "not quiescent". At that point, any attempt to close the drawing programmatically fails.

I'm able to run this command successfully from an menu item.

Any suggestion for how to get around this?

Re: Quiescent state and Command Line

Alexander.Rivilis — Sat, 10 Jun 2017 22:36:12 GMT

You have to create your command with flag CommandFlags.Session:

[CommandMethod("MyTest", CommandFlags.Session)]
public void MyTestNet()
{
//...
}

Re: Quiescent state and Command Line

Anonymous — Sun, 11 Jun 2017 00:49:03 GMT

I need to test this more, but I think this will fix the problem.

What confuses me though is that the flag isQuiescent for the document is still set to false -- probably because my command-line command is running.

I had been looking at this flag previously to determine whether or not I could delete a document or not.

But in this case, even though the flag was set to false, I still seem to be able to delete it.