決定するs whether the 文書 has been 修正するd since the last call to storeToRecoveryFile.
If storeToRecoveryFile has not been called before, this method returns whether the 文書
has been 修正するd since it has been 負担d それぞれ created.
When saving a 開会／開廷／会期, either in 事例／患者 of a 緊急 (when OpenOffice.org 衝突，墜落d), or during a
periodic 開会／開廷／会期 save as configured by the 使用者, storeToRecoveryFile is called for every
文書 where wasModifiedSinceLastSave returns true.
It's 許すd to 器具／実施する this method sloppy, by returning true in 事例／患者s where it is not sure whether
the 文書 現実に has been 修正するd. So, the most simple 実施 could 簡単に 委任する／代表 this call
to ::com::sun::星／主役にする::util::XModifiable::isModified. (井戸／弁護士席, 現実に that's the
second simple 実施, the most simple one would, still egitimately, always return true.)
However, in such a 事例／患者, the 文書 might be saved more often than needed. In particular during the
periodic 開会／開廷／会期 save, this might become a problem when saving is expensive, for a 選び出す／独身 文書
or the sum of all open 文書s.
Upon successful return, the 文書 must be fully initialized. In particular, the
報知係 is not 責任がある calling ::com::sun::星／主役にする::でっちあげる，人を罪に陥れる::XModel::attachResource.
Instead, the 実施 is responsible to do so, if 要求するd.
A default 実施 of this method could 簡単に 委任する／代表 this call to
::com::sun::星／主役にする::でっちあげる，人を罪に陥れる:::XLodable::負担, followed by
::com::sun::星／主役にする::でっちあげる，人を罪に陥れる::XModel::attachResource.
Parameter SourceLocation
明示するs the URL of the 場所 to which the 文書 was 以前 緊急-saved.
Parameter SalvagedFile
明示するs the 初めの URL of the とじ込み／提出する which had been 緊急-saved. If this is empty,
then the とじ込み／提出する should be 回復するd from its 初めの 場所.
Parameter MediaDescriptor
含む／封じ込めるs 付加 arguments for the 負担 過程, for instance an StatusIndicator.
