Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi Pavel,

Pavel Laštovička píše v St 13. 11. 2013 v 13:29 +0100:

I had a plan to take an official Win32 build and after installation replace swlo.dll 
with modified library I built myself. I used this approach successfully once in 
past. However this time Writer crashes (SwDocShell::SwDocShell() calls something in 
sfxlo.dll and a null pointer is referenced). One thing I can think of that might 
cause it is probably different compiler versions used.

Is there some more or less safe way to achieve my goal or should not this approach 
be used at all?

I wouldn't use it - as you can see, anything can go wrong there...

But I am more curious why do you need to do an own swlo.dll in the first
place?  Cannot you just up-stream the functionality you need there?

All the best,
Kendy



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.