From 9f7209dae9b45a26e501559fbefbb9037cada890 Mon Sep 17 00:00:00 2001 From: Vito Caputo Date: Sat, 18 Nov 2023 16:08:15 -0800 Subject: til_builtins/ref: s/render_fragment/render_proxy/ Since ref can be used to reference any module type by path, including ones that don't touch the fragment, it's inappropriate to integrate via render_fragment() since that will cause an implicit clear of the fragment. This is exactly the type of scenario render_proxy was added for, so use it here. --- src/til_builtins.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/til_builtins.c b/src/til_builtins.c index e127261..466c09d 100644 --- a/src/til_builtins.c +++ b/src/til_builtins.c @@ -129,7 +129,7 @@ static void _ref_destroy_context(til_module_context_t *context) } -static void _ref_render_fragment(til_module_context_t *context, til_stream_t *stream, unsigned ticks, unsigned cpu, til_fb_fragment_t **fragment_ptr) +static void _ref_render_proxy(til_module_context_t *context, til_stream_t *stream, unsigned ticks, til_fb_fragment_t **fragment_ptr) { _ref_context_t *ctxt = (_ref_context_t *)context; _ref_setup_t *s = (_ref_setup_t *)context->setup; @@ -174,7 +174,7 @@ static int _ref_setup(const til_settings_t *settings, til_setting_t **res_settin til_module_t _ref_module = { .create_context = _ref_create_context, .destroy_context = _ref_destroy_context, - .render_fragment = _ref_render_fragment, + .render_proxy = _ref_render_proxy, .setup = _ref_setup, .name = "ref", .description = "Context referencer (built-in)", -- cgit v1.2.3