From 03bf99e2dbd0b7aae8b852f5f0e7f2d62a0742a0 Mon Sep 17 00:00:00 2001 From: reduz Date: Tue, 4 Nov 2014 12:57:22 -0800 Subject: [PATCH] Updated tutorial_canvas_layers (markdown) --- tutorial_canvas_layers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tutorial_canvas_layers.md b/tutorial_canvas_layers.md index 1eac66c..20efefd 100644 --- a/tutorial_canvas_layers.md +++ b/tutorial_canvas_layers.md @@ -4,10 +4,10 @@ Regular 2D nodes, such as [Node2D](class_node2d) or [Control](class_control) both inherit from [CanvasItem](class_canvasitem), which is the base for all 2D nodes. CanvasItems can be arranged in trees and they will inherit their transform. This means that, moving the parent, the children will be moved too. -These nodes are placed as direct or indirect children to a [Viewport], and will be displayed through it. -Viewport has a property "canvas_transform", which allows to transform all the CanvasItem hiereachy by a custom [Matrix32](class_matrix32) transform. Nodes such as [Camera2D](class_camera2d), work by changing that transform. +These nodes are placed as direct or indirect children to a [Viewport](class_viewport), and will be displayed through it. +Viewport has a property "canvas_transform" ([Viewport](class_viewport#set_canvas_transform), which allows to transform all the CanvasItem hiereachy by a custom [Matrix32](class_matrix32) transform. Nodes such as [Camera2D](class_camera2d), work by changing that transform. -Changing the canvas transform is useful because it is a lot more efficient than moving the root canvas item. It's a single matrix that offsets the whole 2D drawing, so it's the most efficient way to do scrolling. +Changing the canvas transform is useful because it is a lot more efficient than moving the root canvas item (and hence the whole scene). Canvas transform is a simple matrix that offsets the whole 2D drawing, so it's the most efficient way to do scrolling. ### Not Enough..