Sam Atkins 6edc0cf5ab 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()`.		2023-01-12 11:25:51 +01:00
..
Applets	LibGUI+Everywhere: Use fallible Window::set_main_widget() everywhere :^)	2023-01-06 13:36:02 -07:00
Applications	LibCore+Userland: Don't auto-start new Core::Timers	2023-01-12 11:25:51 +01:00
BuggieBox	Userland: Add the BuggieBox program	2022-11-26 12:41:47 -07:00
Demos	LibGfx: Make Rect::align_within() correct for TopCenter and BottomCenter	2023-01-09 19:54:26 +01:00
DevTools	LibCore+Userland: Don't auto-start new Core::Timers	2023-01-12 11:25:51 +01:00
DynamicLoader	Everywhere: Remove "LibC/" includes, add lint-rule against it	2023-01-07 10:01:37 -07:00
Games	LibCore+Userland: Make Core::Timer::create_single_shot() return ErrorOr	2023-01-12 11:25:51 +01:00
Libraries	LibCore+Userland: Don't auto-start new Core::Timers	2023-01-12 11:25:51 +01:00
Services	LibCore+Userland: Don't auto-start new Core::Timers	2023-01-12 11:25:51 +01:00
Shell	LibCore+Userland: Make Core::Timer::create_single_shot() return ErrorOr	2023-01-12 11:25:51 +01:00
Utilities	LibCore+Userland: Make Core::Timer::create_single_shot() return ErrorOr	2023-01-12 11:25:51 +01:00
CMakeLists.txt	Userland: Add the BuggieBox program	2022-11-26 12:41:47 -07:00