Lock Commandline

[SRSDS]

I think I'm having a problem with some people being too fast for my app to keep up with.

If they are slow it doesn't seem to be a problem but if they are hammering in commands AutoCAD crashes.

Does the comandline wait for instructions to be complete before starting the next?

Or is there a way to disable the commandline until a routine is finished?

Does doclock do this?

[cjneper]

Are you talking about a LISP program?  There is a delay/pause command that slows the program down to allow for user input.

[SRSDS]

It's a Visual Studio app.

I do have a pallette that's a likely cause of the problem but I have spent a lot of time trying to making sure I cancel out of any active command before starting a new one.

I was wondering if the operations from the commandline are stalled (or stacked?) until the previous command has finished.

A script file seems to wait for the previous operation to complete so I assume it does.

[_gile · Accepted solution]

Hi,

If the issue is related to the palette (i.e. a modeless UI), a simple and safe way should be callign custom command methods from the palette as recommended by Kean Walmsley's in this topic.:

"Once again there’s our important rule of thumb when it comes to implementing a modeless UI: rather than manually locking the current document, it’s safer to define a command – which will implicitly lock the current document – and call that from the UI via SendStringToExecute()."

Doing so, you let AutoCAD manage the commands stack.

You can find and example in this tutorial (palette section).

[lena.talkhina]

Hello @SRSDS !

Great to see you here on .NET Forum.

Did you find a solution?
If yes, please click on the "Accept as Solution" button as then also other community users can easily find and benefit from the information.
If not please don't hesitate to give an update here in your topic so all members know what ́s the progression on your question is and what might be helpful to achieve what you ́re looking for. 🙂