modules/{compose,montage,rtv}: exclude builtins

Basically everywhere the
TIL_MODULE_HERMETIC|TIL_MODULE_EXPERIMENTAL exclusions were being
applied needed TIL_MODULE_BUILTIN added.

Mostly this is to prevent randomizers from tripping over builtins
in the available modules lists they draw from.

Because builtins aren't visually interesting by themselves, and
in some cases don't currently even have a means of being
randomized properly like ref's path setting.

This wasn't needed previously since builtins were kept off the
modules list altogether.  But since 1a6210be that changed and
they must be explicitly filtered by flag instead.

Note I deliberately left the rkt case with just a TODO comment.
It's not a randomizer situation, and it might be acceptable to
let rkt just show everything all the time in the module lists.
That whole situation there is for advanced users.

Also note that without this, rtv et al would easily trigger an
assert on NULL setup due to the "none" builtin.  Since there's
still work to be done there in callers properly handling NULL
@res_setup on a successful finalize.  But this commit mitigates
that by avoiding the builtins in the randomizers.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/modules/rkt/rkt.c b/src/modules/rkt/rkt.c
index c84b6ce..d5c42d5 100644
--- a/src/modules/rkt/rkt.c
+++ b/src/modules/rkt/rkt.c
@@ -392,7 +392,7 @@ int rkt_scene_module_setup(const til_settings_t *settings, til_setting_t **res_s
 				     res_setup,
 				     "Scene Module",
 				     RKT_DEFAULT_SCENE_MODULE,
-				     (TIL_MODULE_EXPERIMENTAL | TIL_MODULE_HERMETIC),
+				     (TIL_MODULE_EXPERIMENTAL | TIL_MODULE_HERMETIC), /* TODO: TIL_MODULE_BUILTIN?? rkt is kind of advanced maybe just don't hide things? */
 				     NULL); /* << "rkt" would be wise, but it already gets caught by HERMETIC */
 }