summaryrefslogtreecommitdiff
path: root/vcl/README
diff options
context:
space:
mode:
authorNorbert Thiebaud <nthiebaud@gmail.com>2014-09-12 16:30:40 +0200
committerNorbert Thiebaud <nthiebaud@gmail.com>2014-09-12 19:10:10 +0200
commit91eb279ecdbc8183c18d9b4d856ffadf0148250d (patch)
treef2308efba78d5eb9f155dc0121d177d97c50b375 /vcl/README
parente660e1ed73a6eea3f70fcb36a7bc950c57de80fe (diff)
Revert "vcl: use DeviceCoordinate for GetCaretPositions in sallayout"
Diffstat (limited to 'vcl/README')
-rw-r--r--vcl/README8
1 files changed, 0 insertions, 8 deletions
diff --git a/vcl/README b/vcl/README
index c00a3e152488..65113a62dd5d 100644
--- a/vcl/README
+++ b/vcl/README
@@ -188,11 +188,3 @@ 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.
-