From d3aac1eb52dbf33240a1a8c929d95269c6a8f746 Mon Sep 17 00:00:00 2001 From: xgoff Date: Thu, 2 Aug 2012 12:17:16 -0500 Subject: it looks like love doesn't do anything special with translate et al; they will still affect the canvas even if they are called before it has been set --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 1344511..87749b7 100644 --- a/README.md +++ b/README.md @@ -21,6 +21,7 @@ not to mention: TODOs and/or untested: * consecutive `setCanvas()` calls with a canvas argument, eg: + ```lua love.graphics.setCanvas(canvas1) -- drawing here @@ -30,7 +31,6 @@ love.graphics.setCanvas(canvas3) -- drawing here ``` the background gets saved when `setCanvas()` is called with an argument, but it doesn't get restored until it's called without an argument. currently only one state is saved so it's possible the above code would trash the background. this isn't a problem if you only ever use `renderTo()` because that automatically handles the `setCanvas()` calls -* `love.graphics.translate()`, `love.graphics.rotate()`, `love.graphics.scale()`, and `love.graphics.shear()` are not handled * will changing modes during canvas drawing destroy the contents? beware: i have done only minimal testing of this library so it's possible there are cases where it doesn't work correctly or at all, or that the entire idea is ultimately unworkable! -- cgit v1.2.3-54-g00ecf