I’ve got a report which turned out to be two separate issues. One is a regression from Go-OO 3.2.x, this post is about this part. The other part is about the improvement of both the import/export RTF filter, the bug has some detail on that part as well.

So the problem was that wrapped images (when the image is a frame and not a character) had some extremely small height. I did not notice this bug in LO as an LO-specific extension hides that value, but in Word you can see it:

The fix is to use the height of the containing frame instead of the height of the picture itself, then it’ll look fine:

About four days ago it has been asked on #libreoffice if it’s possible to bind functions to F13..F16 in Calc. The short answer is no, but it turned out it’s pretty trivial to allow that (and of course not only in Calc).

Cedric’s great post is helpful here to find the relevant code. It also truned out that VCL already supports those keys, so only the user interface has to be improvied to export that feature.

The patch is here.

Background: OSL_TRACE() is an internal LibreOffice macro that is like printf(), but it’s only enabled in debug mode. Without it, you would add a debug printf during development:

then you would comment it out when the code started working,:

then remove the comment when it breaks again, etc.

In the past, if you built a LibreOffice module, then you executed:

inside a module, and in case you wanted debug symbols and such messages you built using:

which increased the debug level to 2 (from 0), where 1 is required for debug symbols, 2 for debug messages. (See the OOo wiki page.)

The recent update, why I’m writing this post: Now this has been changed, and debug=t gives you debug symbols only, but no extra debug output. While this is great in most cases, sometimes you still want the old behaviour to get the debug messages. In that case the solution (as pointed out in the mailing list post) is to use:

(Hopefully this post will be handy for who missed that post, like I did the first time.)