HandsOffAfterSave State
Applies to: Outlook 2013 | Outlook 2016
The HandsOffAfterSave state is part of the process of saving the contents of a form to permanent storage. When in this state, the form object should refrain from making changes to the in-memory copies of values of the message's properties, because there may not be another opportunity to save those changes. The following table describes allowed transitions from the HandsOffAfterSave state.
IPersistMessage method | Action | New state |
---|---|---|
IPersistMessage::SaveCompleted(pMessage != NULL) |
Open any embedded objects. The data in the message stored in pMessage is guaranteed to be the same as the message in the previous IPersistMessage::Save call. If the SaveCompleted call succeeds, enter the Normal state. Otherwise, set the last error to E_OUTOFMEMORY and stay in the HandsOffAfterSave state. | Normal or HandsOffAfterSave |
IPersistMessage::SaveCompleted(pMessage == NULL) |
Set the last error to E_INVALIDARG or E_UNEXPECTED. | HandsOffAfterSave |
IPersistMessage::HandsOffMessage, Save, or IPersistMessage::InitNew |
Set the last error to and return E_UNEXPECTED. | HandsOffAfterSave |
IPersistMessage::Load |
Load the form object with data from the target message. This call can occur when the form object is going to the next or previous message in a folder. | Normal |
IPersistMessage::GetLastError |
Return the last error. | HandsOffAfterSave |
Other IPersistMessage : IUnknown methods or methods from other interfaces |
Set the last error to and return E_UNEXPECTED. | HandsOffAfterSave |