On 22 November 2010 21:22, Michael Meeks <michael.me...@novell.com> wrote: > Hi Mattias, > > On Sun, 2010-11-21 at 00:21 +1100, Mattias Johnsson wrote: >> I've been trying to fix a bug in the search and replace code, and >> after a bit of hacking have discovered that in findattr.cxx there's a >> function > > Nice work :-) > >> If I'm understanding things correctly, and I may not be, since the >> search and replace code is quite convoluted, in this case these >> SfxPoolItems are lists of attributes that one can search and replace >> for > > Right ... > >> in this case I'm searching for a specific font size and replacing >> it with another. > > Interesting indeed :-) a new feature for search / replace ? So some of
Not a new feature, but rather fixing this very odd and specific bug: http://qa.openoffice.org/issues/show_bug.cgi?id=115528 OO doesn't seem to like 14 point font :-P. It's not a particularly important bug, but it's proving useful for learning the internals of Writer :-) > these pool items for things like font size are defined in: > > editeng/inc/editeng/fhgtitem.hxx > > as SvxFontHeightItem (I think). Thanks for the tips! On a semi-related note, I'm doing a lot of stepping through the search and replace code trying to track the problem down. Because LO seems to be compiled using -O2 and -O3, there's a lot of optimization which means the way the code gets stepped through is often bizarre, and the values of useful variables have been optimized out by the compiler. Is there a simple option for building the LO project using a lower optimization level? I can't seem to find one... Cheers, Mattias _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice