diff options
| author | Norbert Thiebaud <nthiebaud@gmail.com> | 2014-09-06 16:13:09 +0200 |
|---|---|---|
| committer | Norbert Thiebaud <nthiebaud@gmail.com> | 2014-09-12 01:45:27 +0200 |
| commit | 1b42acdaeae134f94580d6e1eba89da16741d596 (patch) | |
| tree | 882710be2c142cdef62823c9600925ee22f8dab7 /vcl/README | |
| parent | 43638d8428abb8358a703247651fbfc72e47ff72 (diff) | |
vcl: use DeviceCoordinate for GetCaretPositions in sallayout
Change-Id: I5a959e1c3806da713e106c1b0fc8690a6578987b
Diffstat (limited to 'vcl/README')
| -rw-r--r-- | vcl/README | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/vcl/README b/vcl/README index 65113a62dd5d..c00a3e152488 100644 --- a/vcl/README +++ b/vcl/README @@ -188,3 +188,11 @@ other programs, use the "pdfunzip" tool: LD_LIBRARY_PATH=$PWD/instdir/ure/lib workdir/LinkTarget/Executable/pdfunzip input.pdf output.pdf +=== DeviceCoordinate === + +The type DeviceCoordinate is meant to represent coordinate in the native Device space +The implementation is platform dependant. it is a scalar type, but can by int/long/float/double... +Originally such coordinate was represented with int or long... DeviceCoordinate +was introduced to allow for sub-point coordiante (iow float/double), which is +quite important when dealing with HiDPI devices. + |