Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-06-11 | Rename make-colour-rgb to rgb, similar for cmy | Thomas White | |
2022-06-09 | Add 'blackout' | Thomas White | |
2022-06-06 | Rename state-map to state-map->list, add a real state-map | Thomas White | |
2022-01-25 | Separate cue lists from playbacks and crossfades | Thomas White | |
2021-09-11 | at: Clamp continuous attributes to range | Thomas White | |
2021-09-11 | state-source: Clamp continuous attributes to range | Thomas White | |
2021-09-11 | Run state update hook in 'clear-state!' | Thomas White | |
2021-08-08 | Add hook for state updates | Thomas White | |
This includes a "source", intended to be used for avoiding hook users from responding to their own changes. | |||
2021-06-27 | Fixture display: Show selection | Thomas White | |
2021-05-24 | Add hook for state changes on a playback | Thomas White | |
2021-05-22 | Add home-fixture!/blackout! | Thomas White | |
2021-05-16 | Get rid of time parameter and use clock objects for cross-fades | Thomas White | |
Because we can stop a clock object, but not "gettimeofday". | |||
2021-05-13 | Export copy-state | Thomas White | |
2021-05-13 | Avoid mutation of state objects by "set-state-name!" | Thomas White | |
2021-05-10 | Run cues as single atomic operations | Thomas White | |
This avoids a potential situation where one parameter of a fixture is reconfigured before another, which could (in theory) lead to flickering of lights. | |||
2021-05-10 | Make state objects' hash tables immutable with atomic updates | Thomas White | |
States often get updated while they're being scanned out. The obvious case is when manually setting values in the programmer-state, but the more pernicious one is when running a cue. This means that the updates have to be atomic. | |||
2021-05-10 | Split 'base' module up into 'fixture', 'state' and 'scanout' | Thomas White | |