summaryrefslogtreecommitdiff
path: root/src/modules/spiro
diff options
context:
space:
mode:
authorVito Caputo <vcaputo@pengaru.com>2023-06-02 19:55:10 -0700
committerVito Caputo <vcaputo@pengaru.com>2023-06-03 07:42:02 -0700
commit8ceaa22c5e29edbc31bd9d7d8696b179fbf1f5b2 (patch)
tree58b00f955cd5aebcffbcb8f8979e0e840a635323 /src/modules/spiro
parent6ef13be4e8d27f237406d6485d8dfe623db03a5f (diff)
modules/montage: introduce tiles= setting, stop randomizing
Montage would randomize orphaned setting instances for the participating modules @ context create time. This not only produced montage tiles one couldn't configure via settings even if they wanted to, but it also produced partial paths due to the orphaned settings instances. With this commit montage tiles are configurable in the same way compose::layers are; a comma-separated list of modules with settings accompanying them. Randomizing is no longer performed, but if seen via something like rtv, that randomizer will operate on the regular setup machinery to produce randomized montages. One new ability delivered with tiles= is you can specify the same module repeatedly to produce a tiled display of the same thing. Those instances may have the same or different settings, it's totally controllable. This also opens up the future for more interesting things like shiftng ticks in the montage tiles... imagine showing the same module a few times in each row, but offsetting ticks into the future/past in the columns. For ticks-driven modules, you'd see the future/past frames side by side, like a flipbook effect. This leaves rtv as the only til_module_setup_randomize() caller remaining...
Diffstat (limited to 'src/modules/spiro')
0 files changed, 0 insertions, 0 deletions
© All Rights Reserved