summaryrefslogtreecommitdiff
path: root/oox
diff options
context:
space:
mode:
authorMichael Stahl <mstahl@redhat.com>2016-04-27 14:50:05 +0200
committerMichael Stahl <mstahl@redhat.com>2016-04-27 18:46:25 +0200
commitef52ce82bf55b37279e344ea5fef67b4277fb009 (patch)
tree562490b836e03fbd57e712e173c526cb128a8d36 /oox
parentdb4cba76033124cbf1baa560b99700987fcdd3ae (diff)
tdf#89866 tdf#96504 vcl: fix printing of form controls with images
Originally in 2004 commit 0339e43208cd7b98d302e420b39ac32911acaa56 added a "DBG_ASSERT( GetOutDevType() != OUTDEV_PRINTER, "DrawImage(): Images can't be drawn on any mprinter" );" Recently commit f749ffbdf4c007f1a42bcafc9c2723c47bac22d1 made the mistake of trusting this assertion to be correct and added Printer::DrawImage() overrides that do a hard "assert()" now and don't do any drawing. Armin claims that the implementation of OutputDevice::DrawImage() should actually work for Printer as well due to fall-backs and thus the original DBG_ASSERT was misleading. This matters when printing documents that contain form controls such as ImageControl. Additionally, Image::Draw() should not return early when IsDeviceOutputNecessary() is false, because that is the case when printing, where instead a meta-file is recorded. The called OutputDevice::DrawBitmapEx() will check IsDeviceOutputNecessary() internally anyway. This check was actually always there, so i do not understand how this should have worked in LO 4.2, as the bug reporters claim. Change-Id: I92ba19e7036197d1dde88c361f8e1cb59fae3a60
Diffstat (limited to 'oox')
0 files changed, 0 insertions, 0 deletions