From 2a209994505a2737f414a6e7d37cf4cb8bb254d7 Mon Sep 17 00:00:00 2001 From: Thomas White Date: Sun, 17 Jul 2022 22:39:22 +0200 Subject: Add more information about cue lists --- docs/cue-list.rst | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/docs/cue-list.rst b/docs/cue-list.rst index 8716ad8..d17eeee 100644 --- a/docs/cue-list.rst +++ b/docs/cue-list.rst @@ -41,6 +41,40 @@ You can write your own transition effects, if you want some other kind of transition. Documentation pending, but look at snap-transition.scm and crossfade.scm for some examples. +The lighting state does not have to feature a literal ``lighting-state`` form. +Let's say you defined a state somewhere else:: + + (define my-state + (lighting-state + (at spotSR spotSL 50) + (at spotCS 100))) + +You can refer to that state in a cue like this:: + + (cue 3 + my-state + (crossfade 3 5)) + +You can also layer changes on top of the state, by using ``apply-state`` (which +does exactly what its name suggests):: + + (cue 3 + (lighting-state + (apply-state my-state) + (at upstage-spot)) + (crossfade 3 5)) + +You can even make those changes conditional:: + + (define spot-needed #f) + + (cue 3 + (lighting-state + (apply-state my-state) + (when spot-needed + (at upstage-spot))) + (crossfade 3 5)) + Multi-part cues =============== -- cgit v1.2.3