To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93162


User aw changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Wed Oct  1 10:47:51 +0000 
2008 -------
AW: Happens only in SW, in Draw/Impress the font is okay. Problem is that in
ControlPrimitive2D::createBitmapDecomposition where the fallback decompose tries
to create a bitmap displaying the control the xControlView->setZoom(...) still
is somehow related to the twips/100thmm differences between Writer and
Draw/Impress/Calc. This relationship is deeply buried in formcontrols and
toolkit somewhere and has to do with the SetZoom at VCL-Windows and the
following update of the control font. It also has to do with the fact that
controls in edit mode are VCL-Windows and have the application window as parent
already.
To fix this for the fallback - where no MapMode is available by purpose - i have
to query the control for it's implementation, get the VCL-Window and check if
it's parent uses 100thmm. Only then do i need to adapt the zoom at all.
If it's in twips, the positionControlForPaint() which usually happens before
decompose in ViewObjectContactOfUnoControl::createPrimitive2DSequence seems to
be enough and zoom is okay despite rendering to a VDev without any MapMode.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to