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


Today I tried to embed some code to link the content of one text box to
another in Draw. I took heavy inspiration from some existing code in
SdrTextObj::FitFrameToTextSize()
<http://docs.libreoffice.org/svx/html/svdotext_8cxx_source.html#l00205>.
However I get a SIGSEGV in some other part of the code shortly afterwards.

What I tried to do was the following:
- Having two text boxes in the document,
- I tried to copy (a part of) the content from SdrPage::GetObj(0) into
SdrPage::GetObj(1). This occurs in svx's drawinglayer and in particular
in impTextBreakupHandler.
- The text is copied into the outliner of the second text box to be
layouted again (simulating what FitFrameToTextSize above does. An important
difference with that code is that now two different boxes are used).

This is the link to the main commit:
http://cgit.freedesktop.org/libreoffice/core/commit/?h=feature/gsoc14-draw-chained-text-boxes&id=643d9cf5e73e523c88d1b545dd27d98feb1bf088


Here is the seg. fault message:
Program received signal SIGSEGV, Segmentation fault.
0x00007f5cb26d9b5c in ContentAttribs::GetItem (this=0x99999999999999a1,
nWhich=4006)
    at
/home/seriouspillow/Proiects/libreoffice/gsoc/core/editeng/source/editeng/editdoc.cxx:1804
1804    if ( pStyle && ( aAttribSet.GetItemState( nWhich, false ) !=
SFX_ITEM_ON  ) )


Thorsten, any opinions?

Cheers,
Matteo

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.