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()`.
This commit is contained in:
Sam Atkins 2023-01-11 19:36:46 +00:00 committed by Andreas Kling
parent a8cf0c9371
commit 6edc0cf5ab
Notes: sideshowbarker 2024-07-18 04:38:32 +09:00
10 changed files with 12 additions and 8 deletions

View file

@ -110,6 +110,7 @@ ProcessMemoryMapWidget::ProcessMemoryMapWidget()
m_table_view->set_key_column_and_sort_order(0, GUI::SortOrder::Ascending);
m_timer = add<Core::Timer>(1000, [this] { refresh(); });
m_timer->start();
}
void ProcessMemoryMapWidget::set_pid(pid_t pid)