Am 05.01.2014 um 00:18 schrieb Scott Kostyshak <skost...@lyx.org>: > On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt <st.w...@gmx.net> wrote: > >> There are no messages. LyX 2.0.7 is affected too on my system. >> It looks like the problem is a run-time effect and QFontMetrics::maxWidth() >> is the culprit. The attached patch helps. But I don't know if there is >> another >> solution. > > Why doesn't a Git bisect help here? Was the problem triggered by an > update of the Qt libraries?
Short answer: yes, it's triggered by an update of the Qt libraries. The result of QFontMetrics::maxWidth() is simply 0 for the given font. It's a multi-dimensional problem. There are * multiple OS-versions (Mac OS 10.4 .. 10.9) * multiple CPU-archs (i386, ppc, x86_64) * multiple Qt-versions (4.6.x, 4.8.x, 5.x) * multiple Qt-variants (Mac API for Carbon and Cocoa) * multiple tool versions (automake 1.11 .. 1.14 etc.) * multiple LyX versions (lyx-2.0.x, lyx-2.1.x) Not all combinations work, some Qt-version is not compilable on some OS-version or some CPU-architecture. But the biggest hurdle is the tool chain evolution over time. For a git bisect you need a fast machine. The fastest machine I have uses automake 1.14 and so I cannot compile most of the "history of lyx". In fact I'm able to compile on this machine the latest LyX versions only. One complete build of LyX on the elder machine I have - the only device to do a git bisect on - lasts about 10 minutes. There are other font problems with Qt I'm unable to solve, e.g. http://www.lyx.org/trac/ticket/7954 BTW, of course Qt has more than one font rendering engine… It's an a little bit frustrating experience, indeed. Stephan
