Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 1025 - Problem with text-size in the legend box
Summary: Problem with text-size in the legend box
Status: CONFIRMED
Alias: None
Product: VCL TeeChart
Classification: Unclassified
Component: Legend (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-28 09:50 EST by sandra pazos
Modified: 2014-11-28 09:50 EST (History)
0 users

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:


Attachments
ChartTest (1.28 MB, application/x-zip-compressed)
2014-11-28 09:50 EST, sandra pazos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sandra pazos 2014-11-28 09:50:18 EST
Created attachment 354 [details]
ChartTest

There is a problem with Text-Size in the legend box. Basically, the text items are drawn out of bound in GDI canvas when you are using a concrete font height values.Also, the client has detected the problem comments that: 
"The new problem is the TTeeFont where you save the font height as e.g. “Legend.Font.Height = -9” in the resource file. This is OK, but if I use the default height of -11, you don’t save any value. This works fine on all screens with 96dpi fonts. But e.g. on 120dpi you calculate a default font height of -13 instead of -11, because you calculate the font height from the Size parameter in Points. This is a problem, because all other font sizes are stored in pixels. I think, you must define, if you use Points or Pixels when you set the font size. If you use pixels, you must also use a pixel default value for the Font.Height. If you use a Point default value, you must also store the Font.Size in Points in the resource file." 

The attached project reproduces the problem. Maybe the problem is related with bug number id815, http://bugs.teechart.net/show_bug.cgi?id=815