ladybird/UI/Qt/EventLoopImplementationQtEventTarget.cpp

/*
 * Copyright (c) 2023, Gregory Bertilson <zaggy1024@gmail.com>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <UI/Qt/EventLoopImplementationQt.h>
#include <UI/Qt/EventLoopImplementationQtEventTarget.h>

namespace Ladybird {

bool EventLoopImplementationQtEventTarget::event(QEvent* event)
{
    return EventLoopManagerQt::event_target_received_event({}, event);
}

}
Ladybird: Allow posting events to the Qt event loop from other threads Previously, a QTimer was used to start processing of our event queue in the main Qt event loop. Unfortunately, QTimers are not thread-safe, and disallow starting of a timer from a different thread than it was created in. Instead, use a dummy QObject to post a custom QEvent to the main loop from whatever thread we like, and process our event queue when it is received by our dummy object. 2023-07-04 06:37:36 -03:00			`/*`
			`* Copyright (c) 2023, Gregory Bertilson <zaggy1024@gmail.com>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

LibWebView+UI: Move the UI event loops to the UI folder Once upon a time, we needed the UI-specific event loops outside of the UI process. This is no longer the case. Let's move the event loops back to the UI folder to remove the awkward interface library we were left with. 2025-12-05 12:20:44 -03:00			`#include <UI/Qt/EventLoopImplementationQt.h>`
			`#include <UI/Qt/EventLoopImplementationQtEventTarget.h>`
Ladybird: Allow posting events to the Qt event loop from other threads Previously, a QTimer was used to start processing of our event queue in the main Qt event loop. Unfortunately, QTimers are not thread-safe, and disallow starting of a timer from a different thread than it was created in. Instead, use a dummy QObject to post a custom QEvent to the main loop from whatever thread we like, and process our event queue when it is received by our dummy object. 2023-07-04 06:37:36 -03:00
LibWebView+UI: Move the UI event loops to the UI folder Once upon a time, we needed the UI-specific event loops outside of the UI process. This is no longer the case. Let's move the event loops back to the UI folder to remove the awkward interface library we were left with. 2025-12-05 12:20:44 -03:00			`namespace Ladybird {`
Ladybird: Allow posting events to the Qt event loop from other threads Previously, a QTimer was used to start processing of our event queue in the main Qt event loop. Unfortunately, QTimers are not thread-safe, and disallow starting of a timer from a different thread than it was created in. Instead, use a dummy QObject to post a custom QEvent to the main loop from whatever thread we like, and process our event queue when it is received by our dummy object. 2023-07-04 06:37:36 -03:00
			`bool EventLoopImplementationQtEventTarget::event(QEvent* event)`
			`{`
			`return EventLoopManagerQt::event_target_received_event({}, event);`
			`}`

			`}`