OMEdit becomes unresponsive when e.g. checking models

[Per Östlund]

OMEdit becomes completely unresponsive when checking or instantiating a model, without any indication of what OMEdit is doing. For large models this can take some time, so we should show a dialog window that tells the user what is happening and give them the possibility of aborting it.

[Adeel Asghar]

Replying to perost:

OMEdit becomes completely unresponsive when checking or instantiating a model, without any indication of what OMEdit is doing. For large models this can take some time, so we should show a dialog window that tells the user what is happening and give them the possibility of aborting it.

I can make it responsive (this doesn't mean you are allowed to do other tasks during the process). There is no way to cancel the operation because once I have sent the command to OMC I just have to wait for the response.

[Per Östlund]

Replying to adeas31:

I can make it responsive (this doesn't mean you are allowed to do other tasks during the process). There is no way to cancel the operation because once I have sent the command to OMC I just have to wait for the response.

Yes, I'm aware that it might be hard to make it possible to abort the operation. We need some way of interrupting OMC to be able to do something like that. It's possible to just disregard the response from OMC, but then OMC will still perform the operation and waste CPU time.

But popping up a small dialog window that tells the user that OMEdit is busy instantiating/checking/whatever would be a good start. Otherwise the user can't tell whether OMEdit is busy or just hung. Windows helpfully marks the OMEdit window as unresponsive too, which would be nice to avoid.