aboutsummaryrefslogtreecommitdiffstats
path: root/translations
diff options
context:
space:
mode:
authorGravatar Lubomir I. Ivanov <neolit123@gmail.com>2014-07-25 15:59:12 +0300
committerGravatar Dirk Hohndel <dirk@hohndel.org>2014-07-25 07:23:39 -0700
commit050b1b71ffe92b76b98c768e7d30e2a219251a72 (patch)
tree9d8105ffe6302d36da135f4649ff440428e46edc /translations
parentce42e32bceb298201101f1674181b25e380eac0d (diff)
downloadsubsurface-050b1b71ffe92b76b98c768e7d30e2a219251a72.tar.gz
PrintLayout: fix a potential bug in the recent table print update
There is a weird QPicture dependency; we need to offset a page by headingRowHeightD2, which is half the heading height. The same doesn't make sense if we are rendering the table widget directly to the printer-painter. Moving the offset inside 'pageIndexes' is less desirable. The bug itself manifests when a top margin is set on Win32, while on Linux it's more obvious. On new page start, a fixed height from the last dive on the previous page becomes visible even if the math seems correct. Offsetting both the page index and the vertical position at which the QPicture is placed fixes that. If 'table.render(&painter...)' is used the bug also goes away and our 'pageIndexes' start to make sense again, but we want to use QPicture so that the table is in vector. I don't have a good explanation why this happens! Tested on Ubuntu 12.04 and Win7. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'translations')
0 files changed, 0 insertions, 0 deletions