diff options
| author | xgoff <antipotroast@gmail.com> | 2012-08-04 02:09:50 -0500 |
|---|---|---|
| committer | xgoff <antipotroast@gmail.com> | 2012-08-04 02:09:50 -0500 |
| commit | 6de633350db152d47b53ae8ede75d0199bc22b7b (patch) | |
| tree | 1cbf98bbe69bda178d82a41ff18aab06d2b02a18 | |
| parent | 85a581fb73625c04a995a5be6d2995f015b1866a (diff) | |
| download | love2d-fakecanvas-6de633350db152d47b53ae8ede75d0199bc22b7b.tar.gz love2d-fakecanvas-6de633350db152d47b53ae8ede75d0199bc22b7b.tar.bz2 love2d-fakecanvas-6de633350db152d47b53ae8ede75d0199bc22b7b.tar.xz love2d-fakecanvas-6de633350db152d47b53ae8ede75d0199bc22b7b.zip | |
updated
| -rw-r--r-- | README.md | 12 |
1 files changed, 1 insertions, 11 deletions
@@ -22,17 +22,7 @@ not to mention: TODOs and/or untested: -* consecutive `setCanvas()` calls with a canvas argument, eg: - -```lua -love.graphics.setCanvas(canvas1) --- drawing here -love.graphics.setCanvas(canvas2) --- drawing here -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 +* canvases clear themselves automatically, which is unwanted * 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! |