summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorNico Weber <thakis@chromium.org>2021-01-12 15:53:07 -0500
committerAndreas Kling <kling@serenityos.org>2021-01-12 23:32:54 +0100
commitd551263b111bc83e65fa845ef245f43982dfd7ad (patch)
tree7604309027c6336cf8be7c7c8801a6a8a6ad0499 /Documentation
parent545b4879e43472f92bcee5e9142f41cd5fd88e32 (diff)
downloadserenity-d551263b111bc83e65fa845ef245f43982dfd7ad.zip
LibGfx: Make it possible to apply an (integer) scale to a Painter
This adds a scale factor to Painter, which will be used for HighDPI support. It's also a step towards general affine transforms on Painters. All of Painter's public API takes logical coordinates, while some internals deal with physical coordinates now. If scale == 1, logical and physical coordinates are the same. For scale == 2, a 200x100 bitmap would be covered by a logical {0, 0, 100, 50} rect, while its physical size would be {0, 0, 200, 100}. Most of Painter's functions just assert that scale() == 1 is for now, but most functions called by WindowServer are updated to handle arbitrary (integer) scale. Also add a new Demo "LibGfxScaleDemo" that covers the converted functions and that can be used to iteratively add scaling support to more functions. To make Painter's interface deal with logical coordinates only, make translation() and clip_rect() non-public.
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/HighDPI.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/HighDPI.md b/Documentation/HighDPI.md
index 96b1eb1a5a..0043e77a6a 100644
--- a/Documentation/HighDPI.md
+++ b/Documentation/HighDPI.md
@@ -34,4 +34,4 @@ The plan is to have all applications use highdpi backbuffers eventually. It'll t
3. Let apps opt in to high-res window framebuffers, and convert all apps one-by-one
4. Remove high-res window framebuffer opt-in since all apps have it now.
-We're currently before point 0.
+We're currently before point 1.