summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/api.texi11
1 files changed, 3 insertions, 8 deletions
diff --git a/doc/api.texi b/doc/api.texi
index 50ce301..b6aef7b 100644
--- a/doc/api.texi
+++ b/doc/api.texi
@@ -4483,8 +4483,8 @@ and state changes happen within the context of this engine.
Performing a custom draw call could look something like this:
@lisp
-(with-graphics-state ((g:blend-mode blend:alpha)
- (g:texture-0 my-texture))
+(with-graphics-state ((blend-mode blend:alpha)
+ (texture 0 my-texture))
(shader-apply my-shader #:foo 1))
@end lisp
@@ -4502,17 +4502,12 @@ values afterwards.
@end deffn
One additional piece of state that the rendering engine has, that is
-not part of the GPU state, is the current projection matrix:
+not strictly part of the GPU state, is the current projection matrix:
@deffn {Procedure} current-projection
Return the currently bound projection matrix (@pxref{Matrices}).
@end deffn
-@deffn {Syntax} with-projection projection body @dots{}
-Evaluate @var{body} with the current projection matrix bound to
-@var{projection} (@pxref{Matrices}).
-@end deffn
-
@subsubsection Rendering
Chickadee likens a GPU draw call to a Scheme procedure call. A shader