» home
» bugs
» git

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000055 [litestep core] core feature N/A 2008-06-13 11:40 2009-01-16 16:18
Reporter maduin View Status public  
Assigned To
Priority none Resolution open  
Status feedback   Product Version
Summary 0000055: Lengths, Units, and Resolution Independence
Description Problem:

LS modules only support lengths given in pixels, which makes themes very sensitive to screen resolution.

Proposed Solution:

Add a new "length" data type to step.rc with support for multiple units. Furthermore I think that the length data type should be modelled after the length data type used in CSS and other W3C standards.

Examples:

ButtonFontHeight 12pt
LabelWidth 20em
TaskbarX 100px
VWMHeight 1.5cm

CSS includes device units (px), font units (em, ex), and physical units (in, cm, mm, pt, pc).

Implementation:

Modules expect units to be pixels, so in order to minimize the changes to the modules LSAPI should provide functions that automatically convert any length to pixels. Such as:

int GetRCWidth(LPCSTR pszKey, HDC hDC, int nDefault);
int GetRCHeight(LPCSTR pszKey, HDC hDC, int nDefault);

These function convert horizontal and vertical lengths, respectively, into pixels. The hDC parameter is used to convert non-device units into device units and may be NULL (in which case the screen DC is used).

Issues:

Trying to make lengths work with expressions is tricky. It can be done, but it will require some work.
Additional Information http://www.lsdev.org/doku.php?id=lsdev:discussion:displayunits [^]
Tags No tags attached.
Attached Files

- Relationships

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2008-06-13 11:40 jugg New Issue
2008-06-13 11:41 jugg Reporter jugg => maduin
2009-01-16 16:18 ilmcuts Status @10@ => feedback


Copyright © 2000 - 2009 Mantis Group
Powered by Mantis Bugtracker