From 5b6e06928bbd5466d0c65149e8c7e44871e71a8c Mon Sep 17 00:00:00 2001 From: Sakarias Johansson Date: Tue, 21 Mar 2023 23:09:15 +0100 Subject: =?UTF-8?q?=F0=9F=93=96=20Add=20logging=20and=20term=20writes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit println works for a while. Was time to set up something better. Worth to not that there is a big difference between logging and writing to the terminal which is why both slog and console was dragged in. Might seem similar but purpose is not the same. Most of the time the log is interesting during runtime but user messages does not belong in the log. --- racer-tracer/src/image_action/wait_for_signal.rs | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'racer-tracer/src/image_action/wait_for_signal.rs') diff --git a/racer-tracer/src/image_action/wait_for_signal.rs b/racer-tracer/src/image_action/wait_for_signal.rs index 54480ac..0ffe5e7 100644 --- a/racer-tracer/src/image_action/wait_for_signal.rs +++ b/racer-tracer/src/image_action/wait_for_signal.rs @@ -1,8 +1,13 @@ use std::sync::RwLock; +use slog::Logger; use synchronoise::SignalEvent; -use crate::{config::Config, error::TracerError}; +use crate::{ + config::Config, + error::TracerError, + terminal::{write_term, Terminal}, +}; use super::ImageAction; @@ -14,9 +19,11 @@ impl ImageAction for WaitForSignal { _screen_buffer: &RwLock>, event: &SignalEvent, _config: &Config, + _log: Logger, + term: &Terminal, ) -> Result<(), TracerError> { if !event.status() { - println!("Press R to resume."); + write_term!(term, "Press R to resume."); event.wait(); } event.reset(); -- cgit v1.2.3