Wait for SendStringToExecute to complete
While I avoid using SendStringToExecute as much as humanly possible (and then some), this is a cleverly simple solution to the asynchronous problem. Thanks for posting it.
Dave O. 
When you say 'searching the drawing', I assume you mean you are iterating through the model and/or paper space objects correct?
If so, the 'erased' entities will still show up, but they have an IsErased property which should be true.
If so, the 'erased' entities will still show up, but they have an IsErased property which should be true.
Dave O.
Basically, this part goes into your code exactly as is. It declares an event, and a command which will raise the event.
Public Event eCommandComplete As EventHandler
_
Sub CommandComplete()
RaiseEvent eCommandComplete(Nothing, Nothing)
End Sub
Then your first command will do whatever it does to collect points for the window or whatever, set the event handler for the eCommandComplete event to point to your CommandTwo, set up your command string to send to the command line, and notice that the last part of the command string calls the CommandComplete function you just created.
_
Sub SomeCommand()
'get your polyline points or whatever you are doing.
AddHandler eCommandComplete, AddressOf CommandTwo 'set the event handler to CommandTwo
SendStringToExecute("Zoom E CommandComplete ", False, False, False) 'Note the call to CommandComplete at the end.
End Sub
Sub CommandTwo(ByVal sender As Object, ByVal e As EventArgs)
'Iterate the DB and do your post process
End Sub
So the user runs CommandOne, which does some stuff and then calls SendStringToExecute, then ends.
the SendStringToExecute executes. Performing your erase, then calling CommandComplete.
CommandComplete raises your defined event, which calls whatever sub you have assigned the handler to with the AddHandler method.
Technically, you could eliminate the whole event setup and just create two commands, with the sendstring containing the call to the second command directly.
If that wasn't helpful, maybe you should post the pertinent bits of your code and someone can help figure out whats wrong.
Public Event eCommandComplete As EventHandler
Sub CommandComplete()
RaiseEvent eCommandComplete(Nothing, Nothing)
End Sub
Then your first command will do whatever it does to collect points for the window or whatever, set the event handler for the eCommandComplete event to point to your CommandTwo, set up your command string to send to the command line, and notice that the last part of the command string calls the CommandComplete function you just created.
Sub SomeCommand()
'get your polyline points or whatever you are doing.
AddHandler eCommandComplete, AddressOf CommandTwo 'set the event handler to CommandTwo
SendStringToExecute("Zoom E CommandComplete ", False, False, False) 'Note the call to CommandComplete at the end.
End Sub
Sub CommandTwo(ByVal sender As Object, ByVal e As EventArgs)
'Iterate the DB and do your post process
End Sub
So the user runs CommandOne, which does some stuff and then calls SendStringToExecute, then ends.
the SendStringToExecute executes. Performing your erase, then calling CommandComplete.
CommandComplete raises your defined event, which calls whatever sub you have assigned the handler to with the AddHandler method.
Technically, you could eliminate the whole event setup and just create two commands, with the sendstring containing the call to the second command directly.
If that wasn't helpful, maybe you should post the pertinent bits of your code and someone can help figure out whats wrong.
Dave O.
If the plan is to have one function like this:
Sub Whatever
'do stuff
SendStringToExecute()
Do
'nothing
Loop Until Commandcomplete
'do more stuff
End Sub
Then I think the SendStringToExecute will still be waiting to run. Essentially, your code must end, and return control back to the AutoCAD app, before the SendStringToExecute will fire.
Depending on what your arraylist contains, maybe you can temporarily store it in a dictionary for retrieval by the second command in the Event model.
Sub Whatever
'do stuff
SendStringToExecute()
Do
'nothing
Loop Until Commandcomplete
'do more stuff
End Sub
Then I think the SendStringToExecute will still be waiting to run. Essentially, your code must end, and return control back to the AutoCAD app, before the SendStringToExecute will fire.
Depending on what your arraylist contains, maybe you can temporarily store it in a dictionary for retrieval by the second command in the Event model.
Dave O.