godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-04 14:11:02 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5094 from hpnrep6/canvas-layer

Browse Source 
Fix :ref: formatting in Canvas layers
(cherry picked from commit 92ae595888)

# Conflicts:
#	tutorials/2d/canvas_layers.rst
This commit is contained in:
Max Hilbrunner
2021-07-16 13:15:53 +02:00
committed by Max Hilbrunner
parent 4e71e8a79e
commit 7c239e5a50
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tutorials/2d/canvas_layers.rst
View File

@@ -26,11 +26,11 @@ Effects like scrolling are best achieved by manipulating the canvas transform pr
efficient than moving the root canvas item (and hence the whole scene).
Usually though, we don't want *everything* in the game or app to be subject to the canvas
transform. Examples of this are:
transform. For example:
- **Parallax Backgrounds**: Backgrounds that move slower than the rest
of the stage.
- **UI**: Think of a user interface (UI) or Heads-up display (HUD) superimposed on our view of the game world. We want a life counter, score display and other elements to retain their screen positions even when our view of the game world is changing.
- **UI**: Think of a user interface (UI) or head-up display (HUD) superimposed on our view of the game world. We want a life counter, score display and other elements to retain their screen positions even when our view of the game world changes.
- **Transitions**: We may want visual effects used for transitions (fades, blends) to remain at a fixed screen location.
How can these problems be solved in a single scene tree?