On Wed, Jan 13, 2016 at 12:11:05PM +0200, Maxim Monastirsky wrote:
Hi Lionel,
On Wed, 2016-01-13 at 10:27 +0100, Lionel Elie Mamane wrote:
I'm rather worried about the hunks that remove the
OInterceptor::documentEventOccured stuff, which was registered as a
DocumentEventListener. I'm afraid that this is the mechanism that was
used for embedded databases to do the actual "save embedded database
in the ZIP" step.
Do you aware of any specific scenario where it stopped working because
of this commit?
No, "I was worried", not "I found a bug".
For firebird, see
connectivity/source/drivers/firebird/Connection.cxx near the end of
Connection::construct.
The Connection class is a listener, much like OInterceptor was.
Ah, OK, then. The OInterceptor looked like it was rebroadcasting the
event to "sub-listeners". I understand you say that the Connection
class was listening at the same level as the OInterceptor, and was not
such a "sublistener". Then that's alright. Thanks for checking.
If my above worry is not founded, then what was this
OInterceptor::documentEventOccured used for?
It was used to notify XStatusListeners on whether the component is
modified or not, by sending updates for ".uno:Save" with
enabled/disabled states respectively.
And I presume the HSQLDB driver was not such a listener, OK. The list
of listeners were taken from m_pStatCL, and I didn't see this list of
listeners being removed, so it seemed weird to me.
Thanks for reassuring me.
--
Lionel
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.