From 2ff8eac022f397bb1aed28aca376fbe422fc8b3c Mon Sep 17 00:00:00 2001 From: jacqueline Date: Wed, 29 May 2024 14:45:49 +1000 Subject: Start on TTS support by logging the data that will become TTS lines Includes some misc cleanup of haptic double-triggering (or non-triggering), since those cases all end up being TTS event double-reporting, which to me crosses the threshold from "annoying" to "usability issue" --- src/tangara/system_fsm/booting.cpp | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/tangara/system_fsm/booting.cpp') diff --git a/src/tangara/system_fsm/booting.cpp b/src/tangara/system_fsm/booting.cpp index 22a0fcac..feba0dc0 100644 --- a/src/tangara/system_fsm/booting.cpp +++ b/src/tangara/system_fsm/booting.cpp @@ -38,6 +38,7 @@ #include "system_fsm/service_locator.hpp" #include "system_fsm/system_events.hpp" #include "tasks.hpp" +#include "tts/provider.hpp" #include "ui/ui_fsm.hpp" namespace system_fsm { @@ -99,6 +100,7 @@ auto Booting::entry() -> void { std::make_unique(sServices->bg_worker())); sServices->tag_parser(std::make_unique()); sServices->collator(locale::CreateCollator()); + sServices->tts(std::make_unique()); ESP_LOGI(kTag, "init bluetooth"); sServices->bluetooth(std::make_unique( -- cgit v1.2.3