On 2013-05-15 13:10, Stephan Bergmann wrote:
Sure, as I already wrote: "all GUI frameworks have settled on 'confine
relevant code to run in a single event-loop thread' instead" for a
reason. However, doing that change is an endeavor far from trivial...
Perhaps one approach would be
(a) define a special configure flag --find-bad-ui-threadingg
(b) when compiled in that mode, change the SolarMutex code so that it
whinges loudly if acquired from outside the event thread
(c) create a MediumHack which says
Calll configure with --find-bad-ui-threading.
Run LO
Fix places which are calling back into the event thread to use
code like XXXX::pushToEventLoop(.....)
That way, people of medium C++ skill could gradually chip away at the
problem.
Regards, Noel.
Disclaimer: http://www.peralex.com/disclaimer.html
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.