kwin/src/wayland/seat_interface.cpp

1708 lines
51 KiB
C++
Raw Normal View History

/*
SPDX-FileCopyrightText: 2014 Martin Gräßlin <mgraesslin@kde.org>
SPDX-FileCopyrightText: 2020 David Edmundson <davidedmundson@kde.org>
SPDX-License-Identifier: LGPL-2.1-only OR LGPL-3.0-only OR LicenseRef-KDE-Accepted-LGPL
*/
#include "abstract_data_source.h"
#include "seat_interface.h"
#include "seat_interface_p.h"
#include "display.h"
#include "datadevice_interface.h"
#include "datasource_interface.h"
#include "datacontroldevice_v1_interface.h"
#include "datacontrolsource_v1_interface.h"
#include "keyboard_interface.h"
#include "keyboard_interface_p.h"
#include "pointer_interface.h"
#include "pointer_interface_p.h"
#include "primaryselectiondevice_v1_interface.h"
#include "primaryselectionsource_v1_interface.h"
#include "surface_interface.h"
#include "textinput_v2_interface_p.h"
#include "textinput_v3_interface_p.h"
// Qt
#include <QFile>
// Wayland
#ifndef WL_SEAT_NAME_SINCE_VERSION
#define WL_SEAT_NAME_SINCE_VERSION 2
#endif
// linux
2020-04-29 13:59:23 +00:00
#include <config-kwaylandserver.h>
#if HAVE_LINUX_INPUT_H
#include <linux/input.h>
#endif
#include <functional>
2020-04-29 14:56:38 +00:00
namespace KWaylandServer
{
const quint32 SeatInterface::Private::s_version = 5;
const qint32 SeatInterface::Private::s_pointerVersion = 5;
const qint32 SeatInterface::Private::s_touchVersion = 5;
const qint32 SeatInterface::Private::s_keyboardVersion = 5;
SeatInterface::Private::Private(SeatInterface *q, Display *display)
: Global::Private(display, &wl_seat_interface, s_version)
, q(q)
2014-09-18 14:35:28 +00:00
{
textInputV2 = new TextInputV2Interface(q);
textInputV3 = new TextInputV3Interface(q);
2014-09-18 14:35:28 +00:00
}
#ifndef K_DOXYGEN
2014-09-18 14:35:28 +00:00
const struct wl_seat_interface SeatInterface::Private::s_interface = {
getPointerCallback,
getKeyboardCallback,
getTouchCallback,
releaseCallback
};
#endif
SeatInterface::SeatInterface(Display *display, QObject *parent)
: Global(new Private(this, display), parent)
{
Q_D();
connect(this, &SeatInterface::nameChanged, this,
[d] {
2014-09-18 14:35:28 +00:00
for (auto it = d->resources.constBegin(); it != d->resources.constEnd(); ++it) {
d->sendName(*it);
}
}
);
auto sendCapabilitiesAll = [d] {
2014-09-18 14:35:28 +00:00
for (auto it = d->resources.constBegin(); it != d->resources.constEnd(); ++it) {
d->sendCapabilities(*it);
}
};
connect(this, &SeatInterface::hasPointerChanged, this, sendCapabilitiesAll);
connect(this, &SeatInterface::hasKeyboardChanged, this, sendCapabilitiesAll);
connect(this, &SeatInterface::hasTouchChanged, this, sendCapabilitiesAll);
}
SeatInterface::~SeatInterface()
{
Q_D();
2014-09-18 14:35:28 +00:00
while (!d->resources.isEmpty()) {
wl_resource_destroy(d->resources.takeLast());
}
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::bind(wl_client *client, uint32_t version, uint32_t id)
{
wl_resource *r = wl_resource_create(client, &wl_seat_interface, qMin(s_version, version), id);
if (!r) {
wl_client_post_no_memory(client);
return;
}
2014-09-18 14:35:28 +00:00
resources << r;
2014-09-18 14:35:28 +00:00
wl_resource_set_implementation(r, &s_interface, this, unbind);
sendCapabilities(r);
sendName(r);
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::unbind(wl_resource *r)
{
2014-09-18 14:35:28 +00:00
cast(r)->resources.removeAll(r);
}
void SeatInterface::Private::releaseCallback(wl_client *client, wl_resource *resource)
{
Q_UNUSED(client)
wl_resource_destroy(resource);
}
void SeatInterface::Private::updatePointerButtonSerial(quint32 button, quint32 serial)
{
auto it = globalPointer.buttonSerials.find(button);
if (it == globalPointer.buttonSerials.end()) {
globalPointer.buttonSerials.insert(button, serial);
return;
}
it.value() = serial;
}
void SeatInterface::Private::updatePointerButtonState(quint32 button, Pointer::State state)
{
auto it = globalPointer.buttonStates.find(button);
if (it == globalPointer.buttonStates.end()) {
globalPointer.buttonStates.insert(button, state);
return;
}
it.value() = state;
}
bool SeatInterface::Private::updateKey(quint32 key, Keyboard::State state)
{
auto it = keys.states.find(key);
if (it == keys.states.end()) {
keys.states.insert(key, state);
return true;
}
if (it.value() == state) {
return false;
}
it.value() = state;
return true;
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::sendName(wl_resource *r)
{
if (wl_resource_get_version(r) < WL_SEAT_NAME_SINCE_VERSION) {
return;
}
2014-09-18 14:35:28 +00:00
wl_seat_send_name(r, name.toUtf8().constData());
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::sendCapabilities(wl_resource *r)
{
uint32_t capabilities = 0;
2014-09-18 14:35:28 +00:00
if (pointer) {
capabilities |= WL_SEAT_CAPABILITY_POINTER;
}
2014-09-18 14:35:28 +00:00
if (keyboard) {
capabilities |= WL_SEAT_CAPABILITY_KEYBOARD;
}
2014-09-18 14:35:28 +00:00
if (touch) {
capabilities |= WL_SEAT_CAPABILITY_TOUCH;
}
wl_seat_send_capabilities(r, capabilities);
}
2014-09-18 14:35:28 +00:00
SeatInterface::Private *SeatInterface::Private::cast(wl_resource *r)
{
return r ? reinterpret_cast<SeatInterface::Private*>(wl_resource_get_user_data(r)) : nullptr;
}
namespace {
template <typename T>
static
T *interfaceForSurface(SurfaceInterface *surface, const QVector<T*> &interfaces)
{
if (!surface) {
return nullptr;
}
for (auto it = interfaces.constBegin(); it != interfaces.constEnd(); ++it) {
if ((*it)->client() == surface->client()) {
return (*it);
}
}
return nullptr;
}
template <typename T>
static
QVector<T *> interfacesForSurface(SurfaceInterface *surface, const QVector<T*> &interfaces)
{
QVector<T *> ret;
if (!surface) {
return ret;
}
for (auto it = interfaces.constBegin(); it != interfaces.constEnd(); ++it) {
if ((*it)->client() == surface->client() && (*it)->resource()) {
ret << *it;
}
}
return ret;
}
template <typename T>
static
bool forEachInterface(SurfaceInterface *surface, const QVector<T*> &interfaces, std::function<void (T*)> method)
{
if (!surface) {
return false;
}
bool calledAtLeastOne = false;
for (auto it = interfaces.constBegin(); it != interfaces.constEnd(); ++it) {
if ((*it)->client() == surface->client() && (*it)->resource()) {
method(*it);
calledAtLeastOne = true;
}
}
return calledAtLeastOne;
}
}
QVector<PointerInterface *> SeatInterface::Private::pointersForSurface(SurfaceInterface *surface) const
{
return interfacesForSurface(surface, pointers);
}
QVector<KeyboardInterface *> SeatInterface::Private::keyboardsForSurface(SurfaceInterface *surface) const
{
return interfacesForSurface(surface, keyboards);
}
QVector<TouchInterface *> SeatInterface::Private::touchsForSurface(SurfaceInterface *surface) const
{
return interfacesForSurface(surface, touchs);
}
QVector<DataDeviceInterface *> SeatInterface::Private::dataDevicesForSurface(SurfaceInterface *surface) const
{
QVector<DataDeviceInterface *> primarySelectionDevices;
for (auto it = dataDevices.constBegin(); it != dataDevices.constEnd(); ++it) {
if ((*it)->client() == *surface->client()) {
primarySelectionDevices << *it;
}
}
return primarySelectionDevices;
}
void SeatInterface::Private::registerDataDevice(DataDeviceInterface *dataDevice)
{
Q_ASSERT(dataDevice->seat() == q);
dataDevices << dataDevice;
auto dataDeviceCleanup = [this, dataDevice] {
dataDevices.removeOne(dataDevice);
keys.focus.selections.removeOne(dataDevice);
};
QObject::connect(dataDevice, &QObject::destroyed, q, dataDeviceCleanup);
QObject::connect(dataDevice, &DataDeviceInterface::selectionChanged, q,
[this, dataDevice] {
updateSelection(dataDevice);
}
);
QObject::connect(dataDevice, &DataDeviceInterface::selectionCleared, q,
[this, dataDevice] {
updateSelection(dataDevice);
}
);
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
QObject::connect(dataDevice, &DataDeviceInterface::dragStarted, q,
[this, dataDevice] {
const auto dragSerial = dataDevice->dragImplicitGrabSerial();
auto *dragSurface = dataDevice->origin();
if (q->hasImplicitPointerGrab(dragSerial)) {
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
drag.mode = Drag::Mode::Pointer;
drag.sourcePointer = interfaceForSurface(dragSurface, pointers);
drag.transformation = globalPointer.focus.transformation;
} else if (q->hasImplicitTouchGrab(dragSerial)) {
drag.mode = Drag::Mode::Touch;
drag.sourceTouch = interfaceForSurface(dragSurface, touchs);
// TODO: touch transformation
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
} else {
// no implicit grab, abort drag
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
return;
}
auto *originSurface = dataDevice->origin();
const bool proxied = originSurface->dataProxy();
if (!proxied) {
// origin surface
drag.target = dataDevice;
drag.surface = originSurface;
// TODO: transformation needs to be either pointer or touch
drag.transformation = globalPointer.focus.transformation;
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
drag.source = dataDevice;
drag.sourcePointer = interfaceForSurface(originSurface, pointers);
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
drag.destroyConnection = QObject::connect(dataDevice, &QObject::destroyed, q,
[this] {
endDrag(display->nextSerial());
}
);
if (dataDevice->dragSource()) {
drag.dragSourceDestroyConnection = QObject::connect(dataDevice->dragSource(), &AbstractDataSource::aboutToBeDestroyed, q,
[this] {
const auto serial = display->nextSerial();
if (drag.target) {
drag.target->updateDragTarget(nullptr, serial);
drag.target = nullptr;
}
endDrag(serial);
}
);
} else {
drag.dragSourceDestroyConnection = QMetaObject::Connection();
}
dataDevice->updateDragTarget(proxied ? nullptr : originSurface, dataDevice->dragImplicitGrabSerial());
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
emit q->dragStarted();
emit q->dragSurfaceChanged();
}
);
// is the new DataDevice for the current keyoard focus?
if (keys.focus.surface) {
// same client?
if (*keys.focus.surface->client() == dataDevice->client()) {
keys.focus.selections.append(dataDevice);
if (currentSelection) {
dataDevice->sendSelection(currentSelection);
}
}
}
}
void SeatInterface::Private::registerDataControlDevice(DataControlDeviceV1Interface *dataDevice)
{
Q_ASSERT(dataDevice->seat() == q);
dataControlDevices << dataDevice;
auto dataDeviceCleanup = [this, dataDevice] {
dataControlDevices.removeOne(dataDevice);
};
QObject::connect(dataDevice, &QObject::destroyed, q, dataDeviceCleanup);
QObject::connect(dataDevice, &DataControlDeviceV1Interface::selectionChanged, q,
[this, dataDevice] {
// Special klipper workaround to avoid a race
// If the mimetype x-kde-onlyReplaceEmpty is set, and we've had another update in the meantime, do nothing
// See https://github.com/swaywm/wlr-protocols/issues/92
if (dataDevice->selection() && dataDevice->selection()->mimeTypes().contains(QLatin1String("application/x-kde-onlyReplaceEmpty")) &&
currentSelection) {
dataDevice->selection()->cancel();
return;
}
q->setSelection(dataDevice->selection());
}
);
QObject::connect(dataDevice, &DataControlDeviceV1Interface::selectionCleared, q,
[this, dataDevice] {
Q_UNUSED(dataDevice);
q->setSelection(nullptr);
}
);
if (currentSelection) {
dataDevice->sendSelection(currentSelection);
}
}
void SeatInterface::Private::registerPrimarySelectionDevice(PrimarySelectionDeviceV1Interface *primarySelectionDevice)
{
Q_ASSERT(primarySelectionDevice->seat() == q);
primarySelectionDevices << primarySelectionDevice;
auto dataDeviceCleanup = [this, primarySelectionDevice] {
primarySelectionDevices.removeOne(primarySelectionDevice);
keys.focus.primarySelections.removeOne(primarySelectionDevice);
};
QObject::connect(primarySelectionDevice, &QObject::destroyed, q, dataDeviceCleanup);
QObject::connect(primarySelectionDevice, &PrimarySelectionDeviceV1Interface::selectionChanged, q,
[this, primarySelectionDevice] {
updatePrimarySelection(primarySelectionDevice);
}
);
QObject::connect(primarySelectionDevice, &PrimarySelectionDeviceV1Interface::selectionCleared, q,
[this, primarySelectionDevice] {
updatePrimarySelection(primarySelectionDevice);
}
);
// is the new DataDevice for the current keyoard focus?
if (keys.focus.surface) {
// same client?
if (*keys.focus.surface->client() == primarySelectionDevice->client()) {
keys.focus.primarySelections.append(primarySelectionDevice);
if (currentPrimarySelection) {
primarySelectionDevice->sendSelection(currentPrimarySelection);
}
}
}
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
void SeatInterface::Private::endDrag(quint32 serial)
{
auto target = drag.target;
QObject::disconnect(drag.destroyConnection);
QObject::disconnect(drag.dragSourceDestroyConnection);
if (drag.source && drag.source->dragSource()) {
drag.source->dragSource()->dropPerformed();
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (target) {
target->drop();
target->updateDragTarget(nullptr, serial);
}
drag = Drag();
emit q->dragSurfaceChanged();
emit q->dragEnded();
}
void SeatInterface::Private::updateSelection(DataDeviceInterface *dataDevice)
{
// if the update is from the focussed window we should inform the active client
if (!(keys.focus.surface && (*keys.focus.surface->client() == dataDevice->client()))) {
return;
}
q->setSelection(dataDevice->selection());
}
void SeatInterface::Private::updatePrimarySelection(PrimarySelectionDeviceV1Interface *primarySelectionDevice)
{
// if the update is from the focussed window we should inform the active client
if (!(keys.focus.surface && (*keys.focus.surface->client() == primarySelectionDevice->client()))) {
return;
}
q->setPrimarySelection(primarySelectionDevice->selection());
}
void SeatInterface::setHasKeyboard(bool has)
{
Q_D();
2014-09-18 14:35:28 +00:00
if (d->keyboard == has) {
return;
}
2014-09-18 14:35:28 +00:00
d->keyboard = has;
emit hasKeyboardChanged(d->keyboard);
}
void SeatInterface::setHasPointer(bool has)
{
Q_D();
2014-09-18 14:35:28 +00:00
if (d->pointer == has) {
return;
}
2014-09-18 14:35:28 +00:00
d->pointer = has;
emit hasPointerChanged(d->pointer);
}
void SeatInterface::setHasTouch(bool has)
{
Q_D();
2014-09-18 14:35:28 +00:00
if (d->touch == has) {
return;
}
2014-09-18 14:35:28 +00:00
d->touch = has;
emit hasTouchChanged(d->touch);
}
void SeatInterface::setName(const QString &name)
{
Q_D();
2014-09-18 14:35:28 +00:00
if (d->name == name) {
return;
}
2014-09-18 14:35:28 +00:00
d->name = name;
emit nameChanged(d->name);
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::getPointerCallback(wl_client *client, wl_resource *resource, uint32_t id)
{
cast(resource)->getPointer(client, resource, id);
}
void SeatInterface::Private::getPointer(wl_client *client, wl_resource *resource, uint32_t id)
{
// TODO: only create if seat has pointer?
2014-11-26 10:03:32 +00:00
PointerInterface *pointer = new PointerInterface(q, resource);
auto clientConnection = display->getConnection(client);
pointer->create(clientConnection, qMin(wl_resource_get_version(resource), s_pointerVersion), id);
2014-11-26 10:03:32 +00:00
if (!pointer->resource()) {
wl_resource_post_no_memory(resource);
delete pointer;
return;
}
pointers << pointer;
if (globalPointer.focus.surface && globalPointer.focus.surface->client() == clientConnection) {
// this is a pointer for the currently focused pointer surface
globalPointer.focus.pointers << pointer;
pointer->setFocusedSurface(globalPointer.focus.surface, globalPointer.focus.serial);
pointer->d_func()->sendFrame();
if (globalPointer.focus.pointers.count() == 1) {
// got a new pointer
emit q->focusedPointerChanged(pointer);
}
}
QObject::connect(pointer, &QObject::destroyed, q,
[pointer,this] {
pointers.removeAt(pointers.indexOf(pointer));
if (globalPointer.focus.pointers.removeOne(pointer)) {
if (globalPointer.focus.pointers.isEmpty()) {
emit q->focusedPointerChanged(nullptr);
}
}
}
);
emit q->pointerCreated(pointer);
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::getKeyboardCallback(wl_client *client, wl_resource *resource, uint32_t id)
{
cast(resource)->getKeyboard(client, resource, id);
}
void SeatInterface::Private::getKeyboard(wl_client *client, wl_resource *resource, uint32_t id)
{
// TODO: only create if seat has keyboard?
2014-11-26 14:28:47 +00:00
KeyboardInterface *keyboard = new KeyboardInterface(q, resource);
auto clientConnection = display->getConnection(client);
keyboard->create(clientConnection, qMin(wl_resource_get_version(resource), s_keyboardVersion) , id);
2014-11-26 14:28:47 +00:00
if (!keyboard->resource()) {
wl_resource_post_no_memory(resource);
delete keyboard;
return;
}
keyboard->repeatInfo(keys.keyRepeat.charactersPerSecond, keys.keyRepeat.delay);
if (keys.keymap.xkbcommonCompatible) {
keyboard->setKeymap(keys.keymap.content);
}
keyboards << keyboard;
if (keys.focus.surface && keys.focus.surface->client() == clientConnection) {
// this is a keyboard for the currently focused keyboard surface
keys.focus.keyboards << keyboard;
keyboard->setFocusedSurface(keys.focus.surface, keys.focus.serial);
}
QObject::connect(keyboard, &QObject::destroyed, q,
[keyboard,this] {
keyboards.removeAt(keyboards.indexOf(keyboard));
keys.focus.keyboards.removeOne(keyboard);
}
);
emit q->keyboardCreated(keyboard);
}
2014-09-18 14:35:28 +00:00
void SeatInterface::Private::getTouchCallback(wl_client *client, wl_resource *resource, uint32_t id)
{
cast(resource)->getTouch(client, resource, id);
}
void SeatInterface::Private::getTouch(wl_client *client, wl_resource *resource, uint32_t id)
{
// TODO: only create if seat has touch?
TouchInterface *touch = new TouchInterface(q, resource);
auto clientConnection = display->getConnection(client);
touch->create(clientConnection, qMin(wl_resource_get_version(resource), s_touchVersion), id);
if (!touch->resource()) {
wl_resource_post_no_memory(resource);
delete touch;
return;
}
touchs << touch;
if (globalTouch.focus.surface && globalTouch.focus.surface->client() == clientConnection) {
// this is a touch for the currently focused touch surface
globalTouch.focus.touchs << touch;
if (!globalTouch.ids.isEmpty()) {
// TODO: send out all the points
}
}
QObject::connect(touch, &QObject::destroyed, q,
[touch,this] {
touchs.removeAt(touchs.indexOf(touch));
globalTouch.focus.touchs.removeOne(touch);
}
);
emit q->touchCreated(touch);
}
2014-09-18 14:35:28 +00:00
QString SeatInterface::name() const
{
Q_D();
2014-09-18 14:35:28 +00:00
return d->name;
}
bool SeatInterface::hasPointer() const
{
Q_D();
2014-09-18 14:35:28 +00:00
return d->pointer;
}
bool SeatInterface::hasKeyboard() const
{
Q_D();
2014-09-18 14:35:28 +00:00
return d->keyboard;
}
bool SeatInterface::hasTouch() const
{
Q_D();
2014-09-18 14:35:28 +00:00
return d->touch;
}
SeatInterface *SeatInterface::get(wl_resource *native)
{
return Private::get(native);
}
SeatInterface::Private *SeatInterface::d_func() const
{
return reinterpret_cast<Private*>(d.data());
}
QPointF SeatInterface::pointerPos() const
{
Q_D();
return d->globalPointer.pos;
}
void SeatInterface::setPointerPos(const QPointF &pos)
{
Q_D();
if (d->globalPointer.pos == pos) {
return;
}
d->globalPointer.pos = pos;
emit pointerPosChanged(pos);
}
quint32 SeatInterface::timestamp() const
{
Q_D();
return d->timestamp;
}
void SeatInterface::setTimestamp(quint32 time)
{
Q_D();
if (d->timestamp == time) {
return;
}
d->timestamp = time;
emit timestampChanged(time);
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
void SeatInterface::setDragTarget(SurfaceInterface *surface, const QPointF &globalPosition, const QMatrix4x4 &inputTransformation)
{
Q_D();
if (surface == d->drag.surface) {
// no change
return;
}
const quint32 serial = d->display->nextSerial();
if (d->drag.target) {
d->drag.target->updateDragTarget(nullptr, serial);
}
2020-06-23 00:03:49 +00:00
// TODO: technically we can have mulitple data devices
// and we should send the drag to all of them, but that seems overly complicated
// in practice so far the only case for mulitple data devices is for clipboard overriding
d->drag.target = nullptr;
if (d->dataDevicesForSurface(surface).size() > 0) {
d->drag.target = d->dataDevicesForSurface(surface).first();
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (d->drag.mode == Private::Drag::Mode::Pointer) {
setPointerPos(globalPosition);
} else if (d->drag.mode == Private::Drag::Mode::Touch &&
d->globalTouch.focus.firstTouchPos != globalPosition) {
touchMove(d->globalTouch.ids.first(), globalPosition);
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
}
if (d->drag.target) {
d->drag.surface = surface;
d->drag.transformation = inputTransformation;
d->drag.target->updateDragTarget(surface, serial);
} else {
d->drag.surface = nullptr;
}
emit dragSurfaceChanged();
return;
}
void SeatInterface::setDragTarget(SurfaceInterface *surface, const QMatrix4x4 &inputTransformation)
{
Q_D();
if (d->drag.mode == Private::Drag::Mode::Pointer) {
setDragTarget(surface, pointerPos(), inputTransformation);
} else {
Q_ASSERT(d->drag.mode == Private::Drag::Mode::Touch);
setDragTarget(surface, d->globalTouch.focus.firstTouchPos, inputTransformation);
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
}
SurfaceInterface *SeatInterface::focusedPointerSurface() const
{
Q_D();
return d->globalPointer.focus.surface;
}
void SeatInterface::setFocusedPointerSurface(SurfaceInterface *surface, const QPointF &surfacePosition)
{
QMatrix4x4 m;
m.translate(-surfacePosition.x(), -surfacePosition.y());
setFocusedPointerSurface(surface, m);
Q_D();
if (d->globalPointer.focus.surface) {
d->globalPointer.focus.offset = surfacePosition;
}
}
void SeatInterface::setFocusedPointerSurface(SurfaceInterface *surface, const QMatrix4x4 &transformation)
{
Q_D();
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (d->drag.mode == Private::Drag::Mode::Pointer) {
// ignore
return;
}
const quint32 serial = d->display->nextSerial();
QSet<PointerInterface *> framePointers;
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->setFocusedSurface(nullptr, serial);
framePointers << *it;
}
if (d->globalPointer.focus.surface) {
disconnect(d->globalPointer.focus.destroyConnection);
}
d->globalPointer.focus = Private::Pointer::Focus();
d->globalPointer.focus.surface = surface;
auto p = d->pointersForSurface(surface);
d->globalPointer.focus.pointers = p;
if (d->globalPointer.focus.surface) {
d->globalPointer.focus.destroyConnection = connect(surface, &QObject::destroyed, this,
[this] {
Q_D();
d->globalPointer.focus = Private::Pointer::Focus();
emit focusedPointerChanged(nullptr);
}
);
d->globalPointer.focus.offset = QPointF();
d->globalPointer.focus.transformation = transformation;
d->globalPointer.focus.serial = serial;
}
if (p.isEmpty()) {
emit focusedPointerChanged(nullptr);
for (auto p : qAsConst(framePointers))
{
p->d_func()->sendFrame();
}
return;
}
// TODO: signal with all pointers
emit focusedPointerChanged(p.first());
for (auto it = p.constBegin(), end = p.constEnd(); it != end; ++it) {
(*it)->setFocusedSurface(surface, serial);
framePointers << *it;
}
for (auto p : qAsConst(framePointers))
{
p->d_func()->sendFrame();
}
}
PointerInterface *SeatInterface::focusedPointer() const
{
Q_D();
if (d->globalPointer.focus.pointers.isEmpty()) {
return nullptr;
}
return d->globalPointer.focus.pointers.first();
}
void SeatInterface::setFocusedPointerSurfacePosition(const QPointF &surfacePosition)
{
Q_D();
if (d->globalPointer.focus.surface) {
d->globalPointer.focus.offset = surfacePosition;
d->globalPointer.focus.transformation = QMatrix4x4();
d->globalPointer.focus.transformation.translate(-surfacePosition.x(), -surfacePosition.y());
}
}
QPointF SeatInterface::focusedPointerSurfacePosition() const
{
Q_D();
return d->globalPointer.focus.offset;
}
void SeatInterface::setFocusedPointerSurfaceTransformation(const QMatrix4x4 &transformation)
{
Q_D();
if (d->globalPointer.focus.surface) {
d->globalPointer.focus.transformation = transformation;
}
}
QMatrix4x4 SeatInterface::focusedPointerSurfaceTransformation() const
{
Q_D();
return d->globalPointer.focus.transformation;
}
namespace {
static quint32 qtToWaylandButton(Qt::MouseButton button)
{
#if HAVE_LINUX_INPUT_H
static const QHash<Qt::MouseButton, quint32> s_buttons({
{Qt::LeftButton, BTN_LEFT},
{Qt::RightButton, BTN_RIGHT},
{Qt::MiddleButton, BTN_MIDDLE},
{Qt::ExtraButton1, BTN_BACK}, // note: QtWayland maps BTN_SIDE
{Qt::ExtraButton2, BTN_FORWARD}, // note: QtWayland maps BTN_EXTRA
{Qt::ExtraButton3, BTN_TASK}, // note: QtWayland maps BTN_FORWARD
{Qt::ExtraButton4, BTN_EXTRA}, // note: QtWayland maps BTN_BACK
{Qt::ExtraButton5, BTN_SIDE}, // note: QtWayland maps BTN_TASK
{Qt::ExtraButton6, BTN_TASK + 1},
{Qt::ExtraButton7, BTN_TASK + 2},
{Qt::ExtraButton8, BTN_TASK + 3},
{Qt::ExtraButton9, BTN_TASK + 4},
{Qt::ExtraButton10, BTN_TASK + 5},
{Qt::ExtraButton11, BTN_TASK + 6},
{Qt::ExtraButton12, BTN_TASK + 7},
{Qt::ExtraButton13, BTN_TASK + 8}
// further mapping not possible, 0x120 is BTN_JOYSTICK
});
return s_buttons.value(button, 0);
#else
return 0;
#endif
2015-09-02 14:20:10 +00:00
}
}
bool SeatInterface::isPointerButtonPressed(Qt::MouseButton button) const
{
return isPointerButtonPressed(qtToWaylandButton(button));
}
bool SeatInterface::isPointerButtonPressed(quint32 button) const
{
Q_D();
auto it = d->globalPointer.buttonStates.constFind(button);
if (it == d->globalPointer.buttonStates.constEnd()) {
return false;
}
return it.value() == Private::Pointer::State::Pressed ? true : false;
}
void SeatInterface::pointerAxisV5(Qt::Orientation orientation, qreal delta, qint32 discreteDelta, PointerAxisSource source)
{
Q_D();
if (d->drag.mode == Private::Drag::Mode::Pointer) {
// ignore
return;
}
if (d->globalPointer.focus.surface) {
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->axis(orientation, delta, discreteDelta, source);
}
}
}
void SeatInterface::pointerAxis(Qt::Orientation orientation, quint32 delta)
{
Q_D();
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (d->drag.mode == Private::Drag::Mode::Pointer) {
// ignore
return;
}
if (d->globalPointer.focus.surface) {
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->axis(orientation, delta);
}
}
}
void SeatInterface::pointerButtonPressed(Qt::MouseButton button)
{
const quint32 nativeButton = qtToWaylandButton(button);
if (nativeButton == 0) {
return;
}
pointerButtonPressed(nativeButton);
}
void SeatInterface::pointerButtonPressed(quint32 button)
{
Q_D();
const quint32 serial = d->display->nextSerial();
d->updatePointerButtonSerial(button, serial);
d->updatePointerButtonState(button, Private::Pointer::State::Pressed);
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (d->drag.mode == Private::Drag::Mode::Pointer) {
// ignore
return;
}
if (auto *focusSurface = d->globalPointer.focus.surface) {
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->buttonPressed(button, serial);
}
if (focusSurface == d->keys.focus.surface) {
// update the focused child surface
auto p = focusedPointer();
if (p) {
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->d_func()->focusChildSurface(p->d_func()->focusedChildSurface, serial);
}
}
}
}
}
void SeatInterface::pointerButtonReleased(Qt::MouseButton button)
{
const quint32 nativeButton = qtToWaylandButton(button);
if (nativeButton == 0) {
return;
}
pointerButtonReleased(nativeButton);
}
void SeatInterface::pointerButtonReleased(quint32 button)
{
Q_D();
const quint32 serial = d->display->nextSerial();
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
const quint32 currentButtonSerial = pointerButtonSerial(button);
d->updatePointerButtonSerial(button, serial);
d->updatePointerButtonState(button, Private::Pointer::State::Released);
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (d->drag.mode == Private::Drag::Mode::Pointer) {
if (d->drag.source->dragImplicitGrabSerial() != currentButtonSerial) {
// not our drag button - ignore
return;
}
d->endDrag(serial);
return;
}
if (d->globalPointer.focus.surface) {
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->buttonReleased(button, serial);
}
}
}
quint32 SeatInterface::pointerButtonSerial(Qt::MouseButton button) const
{
return pointerButtonSerial(qtToWaylandButton(button));
}
quint32 SeatInterface::pointerButtonSerial(quint32 button) const
{
Q_D();
auto it = d->globalPointer.buttonSerials.constFind(button);
if (it == d->globalPointer.buttonSerials.constEnd()) {
return 0;
}
return it.value();
}
void SeatInterface::relativePointerMotion(const QSizeF &delta, const QSizeF &deltaNonAccelerated, quint64 microseconds)
{
Q_D();
if (d->globalPointer.focus.surface) {
for (auto it = d->globalPointer.focus.pointers.constBegin(), end = d->globalPointer.focus.pointers.constEnd(); it != end; ++it) {
(*it)->relativeMotion(delta, deltaNonAccelerated, microseconds);
}
}
}
void SeatInterface::startPointerSwipeGesture(quint32 fingerCount)
{
Q_D();
if (!d->globalPointer.gestureSurface.isNull()) {
return;
}
d->globalPointer.gestureSurface = QPointer<SurfaceInterface>(d->globalPointer.focus.surface);
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial, fingerCount] (PointerInterface *p) {
p->d_func()->startSwipeGesture(serial, fingerCount);
}
);
}
void SeatInterface::updatePointerSwipeGesture(const QSizeF &delta)
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[delta] (PointerInterface *p) {
p->d_func()->updateSwipeGesture(delta);
}
);
}
void SeatInterface::endPointerSwipeGesture()
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial] (PointerInterface *p) {
p->d_func()->endSwipeGesture(serial);
}
);
d->globalPointer.gestureSurface.clear();
}
void SeatInterface::cancelPointerSwipeGesture()
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial] (PointerInterface *p) {
p->d_func()->cancelSwipeGesture(serial);
}
);
d->globalPointer.gestureSurface.clear();
}
void SeatInterface::startPointerPinchGesture(quint32 fingerCount)
{
Q_D();
if (!d->globalPointer.gestureSurface.isNull()) {
return;
}
d->globalPointer.gestureSurface = QPointer<SurfaceInterface>(d->globalPointer.focus.surface);
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial, fingerCount] (PointerInterface *p) {
p->d_func()->startPinchGesture(serial, fingerCount);
}
);
}
void SeatInterface::updatePointerPinchGesture(const QSizeF &delta, qreal scale, qreal rotation)
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[delta, scale, rotation] (PointerInterface *p) {
p->d_func()->updatePinchGesture(delta, scale, rotation);
}
);
}
void SeatInterface::endPointerPinchGesture()
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial] (PointerInterface *p) {
p->d_func()->endPinchGesture(serial);
}
);
d->globalPointer.gestureSurface.clear();
}
void SeatInterface::cancelPointerPinchGesture()
{
Q_D();
if (d->globalPointer.gestureSurface.isNull()) {
return;
}
const quint32 serial = d->display->nextSerial();
forEachInterface<PointerInterface>(d->globalPointer.gestureSurface.data(), d->pointers,
[serial] (PointerInterface *p) {
p->d_func()->cancelPinchGesture(serial);
}
);
d->globalPointer.gestureSurface.clear();
}
void SeatInterface::keyPressed(quint32 key)
{
Q_D();
d->keys.lastStateSerial = d->display->nextSerial();
if (!d->updateKey(key, Private::Keyboard::State::Pressed)) {
return;
}
if (d->keys.focus.surface) {
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->keyPressed(key, d->keys.lastStateSerial);
}
}
}
void SeatInterface::keyReleased(quint32 key)
{
Q_D();
d->keys.lastStateSerial = d->display->nextSerial();
if (!d->updateKey(key, Private::Keyboard::State::Released)) {
return;
}
if (d->keys.focus.surface) {
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->keyReleased(key, d->keys.lastStateSerial);
}
}
}
SurfaceInterface *SeatInterface::focusedKeyboardSurface() const
{
Q_D();
return d->keys.focus.surface;
}
void SeatInterface::setFocusedKeyboardSurface(SurfaceInterface *surface)
{
Q_D();
const quint32 serial = d->display->nextSerial();
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->setFocusedSurface(nullptr, serial);
}
if (d->keys.focus.surface) {
disconnect(d->keys.focus.destroyConnection);
}
d->keys.focus = Private::Keyboard::Focus();
d->keys.focus.surface = surface;
d->keys.focus.keyboards = d->keyboardsForSurface(surface);
if (d->keys.focus.surface) {
d->keys.focus.destroyConnection = connect(surface, &QObject::destroyed, this,
[this] {
Q_D();
d->keys.focus = Private::Keyboard::Focus();
}
);
d->keys.focus.serial = serial;
// selection?
const QVector<DataDeviceInterface *> dataDevices = d->dataDevicesForSurface(surface);
d->keys.focus.selections = dataDevices;
for (auto dataDevice : dataDevices) {
if (d->currentSelection) {
dataDevice->sendSelection(d->currentSelection);
} else {
dataDevice->sendClearSelection();
}
}
// primary selection
QVector<PrimarySelectionDeviceV1Interface *> primarySelectionDevices;
for (auto it = d->primarySelectionDevices.constBegin(); it != d->primarySelectionDevices.constEnd(); ++it) {
if ((*it)->client() == *surface->client()) {
primarySelectionDevices << *it;
}
}
d->keys.focus.primarySelections = primarySelectionDevices;
for (auto primaryDataDevice : primarySelectionDevices) {
if (d->currentSelection) {
primaryDataDevice->sendSelection(d->currentPrimarySelection);
} else {
primaryDataDevice->sendClearSelection();
}
}
}
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->setFocusedSurface(surface, serial);
}
// focused text input surface follows keyboard
if (hasKeyboard()) {
setFocusedTextInputSurface(surface);
}
}
#if KWAYLANDSERVER_BUILD_DEPRECATED_SINCE(5, 69)
void SeatInterface::setKeymap(int fd, quint32 size)
{
QFile file;
if (!file.open(fd, QIODevice::ReadOnly)) {
return;
}
const char *address = reinterpret_cast<char*>(file.map(0, size));
if (!address) {
return;
}
setKeymapData(QByteArray(address, size));
}
#endif
void SeatInterface::setKeymapData(const QByteArray &content)
{
Q_D();
d->keys.keymap.xkbcommonCompatible = true;
d->keys.keymap.content = content;
for (auto it = d->keyboards.constBegin(); it != d->keyboards.constEnd(); ++it) {
(*it)->setKeymap(content);
}
}
void SeatInterface::updateKeyboardModifiers(quint32 depressed, quint32 latched, quint32 locked, quint32 group)
{
Q_D();
bool changed = false;
#define UPDATE( value ) \
if (d->keys.modifiers.value != value) { \
d->keys.modifiers.value = value; \
changed = true; \
}
UPDATE(depressed)
UPDATE(latched)
UPDATE(locked)
UPDATE(group)
if (!changed) {
return;
}
const quint32 serial = d->display->nextSerial();
d->keys.modifiers.serial = serial;
if (d->keys.focus.surface) {
for (auto it = d->keys.focus.keyboards.constBegin(), end = d->keys.focus.keyboards.constEnd(); it != end; ++it) {
(*it)->updateModifiers(depressed, latched, locked, group, serial);
}
}
}
void SeatInterface::setKeyRepeatInfo(qint32 charactersPerSecond, qint32 delay)
{
Q_D();
d->keys.keyRepeat.charactersPerSecond = qMax(charactersPerSecond, 0);
d->keys.keyRepeat.delay = qMax(delay, 0);
for (auto it = d->keyboards.constBegin(); it != d->keyboards.constEnd(); ++it) {
(*it)->repeatInfo(d->keys.keyRepeat.charactersPerSecond, d->keys.keyRepeat.delay);
}
}
qint32 SeatInterface::keyRepeatDelay() const
{
Q_D();
return d->keys.keyRepeat.delay;
}
qint32 SeatInterface::keyRepeatRate() const
{
Q_D();
return d->keys.keyRepeat.charactersPerSecond;
}
bool SeatInterface::isKeymapXkbCompatible() const
{
Q_D();
return d->keys.keymap.xkbcommonCompatible;
}
#if KWAYLANDSERVER_BUILD_DEPRECATED_SINCE(5, 69)
int SeatInterface::keymapFileDescriptor() const
{
return -1;
}
#endif
#if KWAYLANDSERVER_BUILD_DEPRECATED_SINCE(5, 69)
quint32 SeatInterface::keymapSize() const
{
return 0;
}
#endif
quint32 SeatInterface::depressedModifiers() const
{
Q_D();
return d->keys.modifiers.depressed;
}
quint32 SeatInterface::groupModifiers() const
{
Q_D();
return d->keys.modifiers.group;
}
quint32 SeatInterface::latchedModifiers() const
{
Q_D();
return d->keys.modifiers.latched;
}
quint32 SeatInterface::lockedModifiers() const
{
Q_D();
return d->keys.modifiers.locked;
}
quint32 SeatInterface::lastModifiersSerial() const
{
Q_D();
return d->keys.modifiers.serial;
}
QVector< quint32 > SeatInterface::pressedKeys() const
{
Q_D();
QVector<quint32> keys;
for (auto it = d->keys.states.constBegin(); it != d->keys.states.constEnd(); ++it) {
if (it.value() == Private::Keyboard::State::Pressed) {
keys << it.key();
}
}
return keys;
}
KeyboardInterface *SeatInterface::focusedKeyboard() const
{
Q_D();
if (d->keys.focus.keyboards.isEmpty()) {
return nullptr;
}
return d->keys.focus.keyboards.first();
}
void SeatInterface::cancelTouchSequence()
{
Q_D();
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->cancel();
}
if (d->drag.mode == Private::Drag::Mode::Touch) {
// cancel the drag, don't drop.
if (d->drag.target) {
// remove the current target
d->drag.target->updateDragTarget(nullptr, 0);
d->drag.target = nullptr;
}
// and end the drag for the source, serial does not matter
d->endDrag(0);
}
d->globalTouch.ids.clear();
}
TouchInterface *SeatInterface::focusedTouch() const
{
Q_D();
if (d->globalTouch.focus.touchs.isEmpty()) {
return nullptr;
}
return d->globalTouch.focus.touchs.first();
}
SurfaceInterface *SeatInterface::focusedTouchSurface() const
{
Q_D();
return d->globalTouch.focus.surface;
}
QPointF SeatInterface::focusedTouchSurfacePosition() const
{
Q_D();
return d->globalTouch.focus.offset;
}
bool SeatInterface::isTouchSequence() const
{
Q_D();
return !d->globalTouch.ids.isEmpty();
}
void SeatInterface::setFocusedTouchSurface(SurfaceInterface *surface, const QPointF &surfacePosition)
{
if (isTouchSequence()) {
// changing surface not allowed during a touch sequence
return;
}
Q_ASSERT(!isDragTouch());
Q_D();
if (d->globalTouch.focus.surface) {
disconnect(d->globalTouch.focus.destroyConnection);
}
d->globalTouch.focus = Private::Touch::Focus();
d->globalTouch.focus.surface = surface;
d->globalTouch.focus.offset = surfacePosition;
d->globalTouch.focus.touchs = d->touchsForSurface(surface);
if (d->globalTouch.focus.surface) {
d->globalTouch.focus.destroyConnection = connect(surface, &QObject::destroyed, this,
[this] {
Q_D();
if (isTouchSequence()) {
// Surface destroyed during touch sequence - send a cancel
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->cancel();
}
}
d->globalTouch.focus = Private::Touch::Focus();
}
);
}
}
void SeatInterface::setFocusedTouchSurfacePosition(const QPointF &surfacePosition)
{
Q_D();
d->globalTouch.focus.offset = surfacePosition;
}
qint32 SeatInterface::touchDown(const QPointF &globalPosition)
{
Q_D();
const qint32 id = d->globalTouch.ids.isEmpty() ? 0 : d->globalTouch.ids.lastKey() + 1;
const qint32 serial = display()->nextSerial();
const auto pos = globalPosition - d->globalTouch.focus.offset;
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->down(id, serial, pos);
}
if (id == 0) {
d->globalTouch.focus.firstTouchPos = globalPosition;
}
#if HAVE_LINUX_INPUT_H
if (id == 0 && d->globalTouch.focus.touchs.isEmpty()) {
// If the client did not bind the touch interface fall back
// to at least emulating touch through pointer events.
forEachInterface<PointerInterface>(focusedTouchSurface(), d->pointers,
[this, pos, serial] (PointerInterface *p) {
wl_pointer_send_enter(p->resource(), serial,
focusedTouchSurface()->resource(),
wl_fixed_from_double(pos.x()), wl_fixed_from_double(pos.y()));
wl_pointer_send_motion(p->resource(), timestamp(),
wl_fixed_from_double(pos.x()), wl_fixed_from_double(pos.y()));
wl_pointer_send_button(p->resource(), serial, timestamp(), BTN_LEFT, WL_POINTER_BUTTON_STATE_PRESSED);
p->d_func()->sendFrame();
}
);
}
#endif
d->globalTouch.ids[id] = serial;
return id;
}
void SeatInterface::touchMove(qint32 id, const QPointF &globalPosition)
{
Q_D();
Q_ASSERT(d->globalTouch.ids.contains(id));
const auto pos = globalPosition - d->globalTouch.focus.offset;
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->move(id, pos);
}
if (id == 0) {
d->globalTouch.focus.firstTouchPos = globalPosition;
}
if (id == 0 && d->globalTouch.focus.touchs.isEmpty()) {
// Client did not bind touch, fall back to emulating with pointer events.
forEachInterface<PointerInterface>(focusedTouchSurface(), d->pointers,
[this, pos] (PointerInterface *p) {
wl_pointer_send_motion(p->resource(), timestamp(),
wl_fixed_from_double(pos.x()), wl_fixed_from_double(pos.y()));
}
);
}
emit touchMoved(id, d->globalTouch.ids[id], globalPosition);
}
void SeatInterface::touchUp(qint32 id)
{
Q_D();
Q_ASSERT(d->globalTouch.ids.contains(id));
const qint32 serial = display()->nextSerial();
if (d->drag.mode == Private::Drag::Mode::Touch &&
d->drag.source->dragImplicitGrabSerial() == d->globalTouch.ids.value(id)) {
// the implicitly grabbing touch point has been upped
d->endDrag(serial);
}
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->up(id, serial);
}
#if HAVE_LINUX_INPUT_H
if (id == 0 && d->globalTouch.focus.touchs.isEmpty()) {
// Client did not bind touch, fall back to emulating with pointer events.
const quint32 serial = display()->nextSerial();
forEachInterface<PointerInterface>(focusedTouchSurface(), d->pointers,
[this, serial] (PointerInterface *p) {
wl_pointer_send_button(p->resource(), serial, timestamp(), BTN_LEFT, WL_POINTER_BUTTON_STATE_RELEASED);
}
);
}
#endif
d->globalTouch.ids.remove(id);
}
void SeatInterface::touchFrame()
{
Q_D();
for (auto it = d->globalTouch.focus.touchs.constBegin(), end = d->globalTouch.focus.touchs.constEnd(); it != end; ++it) {
(*it)->frame();
}
}
bool SeatInterface::hasImplicitTouchGrab(quint32 serial) const
{
Q_D();
if (!d->globalTouch.focus.surface) {
// origin surface has been destroyed
return false;
}
return d->globalTouch.ids.key(serial, -1) != -1;
}
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
bool SeatInterface::isDrag() const
{
Q_D();
return d->drag.mode != Private::Drag::Mode::None;
}
bool SeatInterface::isDragPointer() const
{
Q_D();
return d->drag.mode == Private::Drag::Mode::Pointer;
}
bool SeatInterface::isDragTouch() const
{
Q_D();
return d->drag.mode == Private::Drag::Mode::Touch;
}
bool SeatInterface::hasImplicitPointerGrab(quint32 serial) const
{
Q_D();
const auto &serials = d->globalPointer.buttonSerials;
for (auto it = serials.constBegin(), end = serials.constEnd(); it != end; it++) {
[server] Implement support for drag'n'drop through pointer device Summary: How drag'n'drop works on Wayland: When a surface has a pointer grab and a button pressed on the surface (implicit grab) the client can initiate a drag'n'drop operation on the data device. For this the client needs to provide a data source describing the data to be transmitted with the drag'n'drop operation. When a drag'n'drop operation is active all pointer events are interpreted as part of the drag'n'drop operation, the pointer device is grabbed. Pointer events are no longer sent to the focused pointer but to the focused data device. When the pointer moves to another surface an enter event is sent to a data device for that surface and a leave event is sent to the data device previously focused. An enter event carries a data offer which is created from the data source for the operation. During pointer motion there is a feedback mechanism. The data offer can signal to the data source that it can or cannot accept the data at the current pointer position. This can be used by the client being dragged from to update the cursor. The drag'n'drop operation ends with the implicit grab being removed, that is the pressed pointer button which triggered the operation gets released. The server sends a drop event to the focused data device. The data transfer can now be started. For that the receiving client creates a pipe and passes the file descriptor through the data offer to the sending data source. The sending client will write into the file descriptor and close it to finish the transfer. Drag'n'drop could also be initiated through a touch device grab, but this is not yet implemented. The implementation in this change focuses on the adjustments for pointer. For the user of the library drag'n'drop is implemented in the SeatInterface. Signals are emitted whenever drag is started or ended. The interaction for pointer events hardly changes. Motion, button press and button release can still be indicated in the same way. If a button release removes the implicit grab the drop is automatically performed, without the user of the library having to do anything. The only change during drag and drop for the library user is that setFocusedPointerSurface is blocked. To update the current drag target the library user should use setDragTarget. Sending the enter/leave to the data device gets performed automatically. The data device which triggered the drag and drop operation is exposed in the SeatInterface. The user of the library should make sure to render the additional drag icon provided on the data device. At least QtWayland based applications will freeze during drag and drop if the icon doesn't get rendered. The implementation is currently still lacking the client side and due to that also auto test. It's currently only tested with QtWayland clients. Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1046
2016-03-01 06:49:04 +00:00
if (it.value() == serial) {
return isPointerButtonPressed(it.key());
}
}
return false;
}
QMatrix4x4 SeatInterface::dragSurfaceTransformation() const
{
Q_D();
return d->drag.transformation;
}
SurfaceInterface *SeatInterface::dragSurface() const
{
Q_D();
return d->drag.surface;
}
PointerInterface *SeatInterface::dragPointer() const
{
Q_D();
if (d->drag.mode != Private::Drag::Mode::Pointer) {
return nullptr;
}
return d->drag.sourcePointer;
}
DataDeviceInterface *SeatInterface::dragSource() const
{
Q_D();
return d->drag.source;
}
void SeatInterface::setFocusedTextInputSurface(SurfaceInterface *surface)
{
Q_D();
const quint32 serial = d->display->nextSerial();
if (d->focusedTextInputSurface) {
disconnect(d->focusedSurfaceDestroyConnection);
}
if (d->focusedTextInputSurface != surface){
d->textInputV2->d->sendLeave(serial, d->focusedTextInputSurface);
d->textInputV3->d->sendLeave(d->focusedTextInputSurface);
d->focusedTextInputSurface = surface;
emit focusedTextInputSurfaceChanged();
}
if (d->focusedTextInputSurface) {
d->focusedSurfaceDestroyConnection = connect(surface, &SurfaceInterface::aboutToBeDestroyed, this,
[this] {
setFocusedTextInputSurface(nullptr);
}
);
}
d->textInputV2->d->sendEnter(surface, serial);
d->textInputV3->d->sendEnter(surface);
// TODO: setFocusedSurface like in other interfaces
}
SurfaceInterface *SeatInterface::focusedTextInputSurface() const
{
Q_D();
return d->focusedTextInputSurface;
}
TextInputV2Interface *SeatInterface::textInputV2() const
{
Q_D();
return d->textInputV2;
}
TextInputV3Interface *SeatInterface::textInputV3() const
{
Q_D();
return d->textInputV3;
}
AbstractDataSource *SeatInterface::selection() const
{
Q_D();
return d->currentSelection;
}
void SeatInterface::setSelection(AbstractDataSource *selection)
{
Q_D();
if (d->currentSelection == selection) {
return;
}
if (d->currentSelection) {
d->currentSelection->cancel();
disconnect(d->currentSelection, nullptr, this, nullptr);
}
if (selection) {
auto cleanup = [this]() {
setSelection(nullptr);
};
connect(selection, &DataSourceInterface::aboutToBeDestroyed, this, cleanup);
}
d->currentSelection = selection;
for (auto focussedSelection: qAsConst(d->keys.focus.selections)) {
if (selection) {
focussedSelection->sendSelection(selection);
} else {
focussedSelection->sendClearSelection();
}
}
for (auto control : qAsConst(d->dataControlDevices)) {
if (selection) {
control->sendSelection(selection);
} else {
control->sendClearSelection();
}
}
emit selectionChanged(selection);
}
void SeatInterface::setPrimarySelection(AbstractDataSource *selection)
{
Q_D();
if (d->currentPrimarySelection == selection) {
return;
}
if (d->currentPrimarySelection) {
d->currentPrimarySelection->cancel();
disconnect(d->currentPrimarySelection, nullptr, this, nullptr);
}
if (selection) {
auto cleanup = [this]() {
setPrimarySelection(nullptr);
};
connect(selection, &DataSourceInterface::aboutToBeDestroyed, this, cleanup);
}
d->currentPrimarySelection = selection;
for (auto focussedSelection: qAsConst(d->keys.focus.primarySelections)) {
if (selection) {
focussedSelection->sendSelection(selection);
} else {
focussedSelection->sendClearSelection();
}
}
emit primarySelectionChanged(selection);
}
}