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


Hi Krisztian,

Krisztian Pinter píše v So 02. 03. 2013 v 12:05 +0100:

I'd like to request some help with implementing a feature. I'm a bsc
student working as a trainee and I'm still very unfamiliar with the LO
codebase.
I was given the task to implement
this: https://bugs.freedesktop.org/show_bug.cgi?id=47011

Thank you for that, great work so far!

I have added a checkbox in Tools -> Options -> Load/Save -> General
with the text "Save document when saving AutoRecovery information",
copying how other checkboxes work. I triple checked everything, but
this checkbox still won't save its state.

Unfortunately cannot check myself ATM, but have you tried to debug that
a bit?

First you need to rebuild the relevant part with debug info, like:

make sfx2.clean
make debug=true sfx2

If you have a developer installation (you have done 'make dev-install'),
then you just run LO in the debugger:

cd installation/program
. ooenv
gdb --tui ./soffice.bin

[Some do not like the --tui (text user interface), but it works for me
pretty well when you get used to pressing Ctrl-L when the screen gets
messed up :-)]

Set the breakpoint where you'd expect the code to appear using 'break',
and then start LO using 'run'.

If it is hit, you can investigate what is going on; if not, some further
investigation is needed I am afraid - let us know then.

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.