ladybird/UI/Qt/EventLoopImplementationQtEventTarget.h

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

#pragma once

#include <QEvent>
#include <QObject>

namespace Ladybird {

class EventLoopImplementationQtEventTarget final : public QObject {
    Q_OBJECT

public:
    virtual bool event(QEvent* event) override;
};

}
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`
			`*/`

			`#pragma once`

Everywhere: Move the Ladybird folder to UI 2024-11-09 14:50:33 -03:00			`#include <QEvent>`
LibWebView+Services+UI: Move the EventLoop implementations to LibWebView We currently compile the Qt event loop files multiple times, for every target which wants to use them. This patch moves these to LibWebView as a central location to avoid this. 2024-11-10 11:23:10 -03:00			`#include <QObject>`
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
			`class EventLoopImplementationQtEventTarget final : public QObject {`
			`Q_OBJECT`

			`public:`
			`virtual bool event(QEvent* event) override;`
			`};`

			`}`