To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=41990
User mav changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Feb 4 07:29:05 -0800
2005 -------
>From my point of view setting of m_nObjectState in
OCommonEmbeddedObject::SwitchStateTo_Impl before real switch to the active state
would be a hack, that would only workaround the problem. Theoretically it is
still possible to have a case when a different target state is requested while
the object is activating.
The problem seems to be either that the timer is activated in the same ( main )
thread or the second call is done from the code activated by notification, so
the mutex lock just does not guard the method. Such a second call must be
handled correctly in the embedded object.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
