kdeconnect-kde/core/kdeconnectplugin.h
Alexander Lohnau 1631ada5b3 Simplify KDEConnectPlugin::recievePacket
- We do not need the return type. If a plugin declares it can handle the
  packet it should do so. We don't have any fallback logic in place and
  the packet types are namespaced with the plugin IDs anyway.

- Provide a default implementation with a warning, not all plugins need
  to overwrite this
2023-08-03 20:49:44 +02:00

58 lines
1.4 KiB
C++

/**
* SPDX-FileCopyrightText: 2013 Albert Vaca <albertvaka@gmail.com>
*
* SPDX-License-Identifier: GPL-2.0-only OR GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
*/
#ifndef KDECONNECTPLUGIN_H
#define KDECONNECTPLUGIN_H
#include <QObject>
#include <QVariantList>
#include "device.h"
#include "kdeconnectcore_export.h"
#include "kdeconnectpluginconfig.h"
#include "networkpacket.h"
struct KdeConnectPluginPrivate;
class KDECONNECTCORE_EXPORT KdeConnectPlugin : public QObject
{
Q_OBJECT
public:
KdeConnectPlugin(QObject *parent, const QVariantList &args);
~KdeConnectPlugin() override;
const Device *device();
Device const *device() const;
bool sendPacket(NetworkPacket &np) const;
KdeConnectPluginConfig *config() const;
virtual QString dbusPath() const;
QString iconName() const;
public Q_SLOTS:
/**
* Returns true if it has handled the packet in some way
* device.sendPacket can be used to send an answer back to the device
*/
virtual void receivePacket(const NetworkPacket &np);
/**
* This method will be called when a device is connected to this computer.
* The plugin could be loaded already, but there is no guarantee we will be able to reach the device until this is called.
*/
virtual void connected()
{
}
private:
QScopedPointer<KdeConnectPluginPrivate> d;
};
#endif