From 6edc0cf5ab2fce211318b5d4f83e319897b621e5 Mon Sep 17 00:00:00 2001 From: Sam Atkins Date: Wed, 11 Jan 2023 19:36:46 +0000 Subject: LibCore+Userland: Don't auto-start new Core::Timers This was unintuitive, and only useful in a few cases. In the majority, users had to immediately call `stop()`, and several who did want the timer started would call `start()` on it immediately anyway. Case in point: There are only two places I had to add a manual `start()`. --- Userland/Applications/SystemMonitor/main.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'Userland/Applications/SystemMonitor/main.cpp') diff --git a/Userland/Applications/SystemMonitor/main.cpp b/Userland/Applications/SystemMonitor/main.cpp index e01aa4f254..e1b110d38c 100644 --- a/Userland/Applications/SystemMonitor/main.cpp +++ b/Userland/Applications/SystemMonitor/main.cpp @@ -328,6 +328,7 @@ ErrorOr serenity_main(Main::Arguments arguments) }; update_stats(); auto& refresh_timer = window->add(frequency * 1000, move(update_stats)); + refresh_timer.start(); auto selected_id = [&](ProcessModel::Column column) -> pid_t { if (process_table_view.selection().is_empty()) -- cgit v1.2.3