mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-05-07 11:42:51 +00:00
7b963e1e98
Things such as timers and notifiers aren't specific to one instance of Core::EventLoop, so let's not tie them down to EventLoopImplementation. Instead, move those APIs + signals & a few other things to a new EventLoopManager interface. EventLoopManager also knows how to create a new EventLoopImplementation object.
48 lines
1.2 KiB
C++
48 lines
1.2 KiB
C++
/*
|
|
* Copyright (c) 2023, Andreas Kling <kling@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <AK/NonnullOwnPtr.h>
|
|
#include <LibCore/Event.h>
|
|
#include <LibCore/EventLoopImplementation.h>
|
|
#include <LibCore/EventLoopImplementationUnix.h>
|
|
#include <LibCore/ThreadEventQueue.h>
|
|
|
|
namespace Core {
|
|
|
|
EventLoopImplementation::EventLoopImplementation() = default;
|
|
|
|
EventLoopImplementation::~EventLoopImplementation() = default;
|
|
|
|
static EventLoopManager* s_event_loop_manager;
|
|
EventLoopManager& EventLoopManager::the()
|
|
{
|
|
if (!s_event_loop_manager)
|
|
s_event_loop_manager = new EventLoopManagerUnix;
|
|
return *s_event_loop_manager;
|
|
}
|
|
|
|
void EventLoopManager::install(Core::EventLoopManager& manager)
|
|
{
|
|
s_event_loop_manager = &manager;
|
|
}
|
|
|
|
EventLoopManager::EventLoopManager()
|
|
: m_thread_event_queue(ThreadEventQueue::current())
|
|
{
|
|
}
|
|
|
|
EventLoopManager::~EventLoopManager() = default;
|
|
|
|
void EventLoopManager::post_event(Object& receiver, NonnullOwnPtr<Event>&& event)
|
|
{
|
|
m_thread_event_queue.post_event(receiver, move(event));
|
|
|
|
// Wake up this EventLoopImplementation if this is a cross-thread event posting.
|
|
if (&ThreadEventQueue::current() != &m_thread_event_queue)
|
|
wake();
|
|
}
|
|
|
|
}
|