3 helper class and a site were using OClearableGuard on the SolarMutex
None of these actually needed the Clearable feature, so
they were replaced by a simple SolarMutexGuard.
2009-04-08 21:06:02 +0200 fs r270660 : #i100956# hold the assigned events in the ModelImpl, not in the DatabaseDocument, so they survive the model being destroyed
2009-04-08 12:40:13 +0200 b_michaelsen r270635 : #i100928# Opening the Tools->Options->Improvement Program Tabpage on first start accidently activates Usage Tracking
2009-04-07 12:56:29 +0200 fs r270594 : #i100866# don't call into the StatusIndicator with our mutex locked
2009-04-07 10:31:02 +0200 fs r270581 : #i100866# impl_import_throw -> impl_import_nolck_throw
2009-04-06 22:53:10 +0200 fs r270575 : #i100866# some more mutex lock tweaking
2009-04-06 22:01:51 +0200 fs r270573 : #i100861# load the Show/Hide strings from the proper (an existing, in particular) resource
2009-04-06 12:43:16 +0200 fs r270537 : #i100866# notifyEvent: instantiate the ScriptDocument only when required.
2009-04-06 12:42:03 +0200 fs r270536 : #i100866#
rework how and when it is determined whether the DBDoc or sub documents contain
scripts/macros. In particular, cache this information in the ODatabaseDocument
implementation, so that queryInterface does not need to lock the mutex
2009-04-03 10:21:02 +0200 oj r270465 : #i100789# surround uno call with try catch
2009-04-03 09:18:37 +0200 oj r270453 : #i100789# check token is not null
2007/07/31 08:52:40 fs 1.1.2.2: #i73331# +onDocumentModeChanged
2007/07/30 13:38:10 fs 1.1.2.1: #i73331# wrapper for notifying document-related events, obtained from a UNO instead of an SFX source
