Issue 93162 - wrong control font in design mode
Summary: wrong control font in design mode
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: DEV300m30
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: wolframgarten
QA Contact: issues@dba
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2008-08-27 09:30 UTC by Frank Schönheit
Modified: 2009-01-19 09:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
document to reproduce the bug case (7.68 KB, application/vnd.oasis.opendocument.text)
2008-08-27 09:31 UTC, Frank Schönheit 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2008-08-27 09:30:37 UTC 
- open the attached document
=> note the font of the button in the document is rather large
- switch off the control design mode (in the "Form Controls" toolbar)
=> the font on the control is much smaller now

In fact, the font in alive mode is the proper one, the font in design mode is wrong.
Comment 1 Frank Schönheit 2008-08-27 09:31:02 UTC 
Created attachment 56037 [details]
document to reproduce the bug case
Comment 2 Frank Schönheit 2008-08-27 09:31:28 UTC 
adding regression keyword (probably caused by aw033), targeting
Comment 3 Armin Le Grand 2008-10-01 11:47:51 UTC 
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.
Comment 4 Armin Le Grand 2008-10-01 13:42:25 UTC 
AW: Checked in temporary solution, works. Maybe necessary to rework parts of
FormControl visualisations.
Comment 5 Armin Le Grand 2008-10-08 12:29:08 UTC 
AW->WG: Please verify. Fonts for form controls (e.g. simple button) should have
the same font visualisation in SW and SD now as in DEV300 m29 (or the 3.0
release path if You have one installed already)
Comment 6 wolframgarten 2008-10-08 13:06:17 UTC 
Verified in CWS.
Comment 7 wolframgarten 2009-01-19 09:31:32 UTC 
Tested in m38. Closed.