aboutsummaryrefslogtreecommitdiff
path: root/Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd
diff options
context:
space:
mode:
authorTravis CI <zmoelnig@travis-ci.umlaeute.mur.at>2017-12-05 19:53:02 +0000
committerTravis CI <zmoelnig@travis-ci.umlaeute.mur.at>2017-12-05 19:53:02 +0000
commitb84d4cc6b9c97874a958bc28ae2d6fd0da9bd833 (patch)
tree51fb2a639e51af9aa38fc694ae9b41ba123a096f /Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd
parent48351101d6169c18542224f9efa8d26f0af4201a (diff)
Gem ff2a6654059bb2881be49407cfaaee188a9aec42 osx/i386
built 'master:ff2a6654059bb2881be49407cfaaee188a9aec42' for osx/i386
Diffstat (limited to 'Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd')
-rw-r--r--Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd2
1 files changed, 1 insertions, 1 deletions
diff --git a/Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd b/Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd
index 69ef470..6738415 100644
--- a/Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd
+++ b/Gem/examples/07.texture/11.multiples_gemhead_in_a_framebuffer.pd
@@ -33,7 +33,7 @@
#X text 201 238 (it change even after a new gemhead \, this is not
very intuitive);
#X text 323 283 <- continue the render chain. The gemhead did not start
-a new gemchain \, because it is banged during a frambuffer rendering
+a new gemchain \, because it is banged during a framebuffer rendering
;
#X text 113 10 This example show how to draw multiples gemhead in a
single framebuffer;