These additional steps will make your application integrate completely with the MDI.
- Consider migrating your AcEditorReactor::commandXxx() and AcEditorReactor::LispXxx() callbacks to work instead from AcDocMananagerReactor::documentLockModeWillChange() and AcDocMananagerReactor::documentLockModeChanged() notifications. Then they will account for application execution context operations that were previously difficult to detect by ObjectARX applications.
- Avoid using acedCommandS()/acedCommandC(). Use AcApDocManager::setStringToExecute() instead, because it has a document parameter.
- Avoid using the kLoadDwg and kUnloadDwg cases, and use the documentToBeCreated() and documentToBeDestroyed() reactors instead.
- Support the document-independent database feature. For more information, see Document-Independent Databases.
- Support multi-document commands. For more information, see Multi-Document Commands.
- Support all events that occur within the application execution context. For more information, see Application Execution Context.