syncfront/krfb
1
0
Fork 0
mirror of https://github.com/KDE/krfb synced 2026-07-01 07:31:16 -07:00
Code Issues Packages Projects Releases Wiki Activity
Files
f5df4d7603d9ecc42e42ae09e569da01a627b1c5
krfb/framebuffers/xcb/xcb_framebufferplugin.cpp

25 lines
597 B
C++
Raw Normal View History

Implement XCB framebuffer plugin (port from x11) Previously used x11 plugin does not compile with Qt5, because Qt5 does not use Xlib, it uses xcb. Rewrite screen capture plugin from Xlib to xcb. I made xcb libs compile required dependency, but availability of X shared memory extension is checked at runtime. It is used to effectively get image pixels data, instead of transfering 8Mb over the wire. Xdamage is used to limit image getting operations only within actually changed rectangles of screen. BUG: 377998 Tested on single-monitor system and dual-monitor, where primary monitor does not start at (0,0) coordinate. Image transfer works fine. Dual-monitor only has problems with receiving mouse cursor position and clicks, but this should be fixed outside of framebuffer plugin. Differential Revision: https://phabricator.kde.org/D5211
2017-06-15 23:20:48 +02:00
/* This file is part of the KDE project
Convert license statements to SPDX
2024-08-08 01:08:31 +02:00
SPDX-FileCopyrightText: 2017 Alexey Min <alexey.min@gmail.com>
SPDX-License-Identifier: GPL-2.0-or-later
Implement XCB framebuffer plugin (port from x11) Previously used x11 plugin does not compile with Qt5, because Qt5 does not use Xlib, it uses xcb. Rewrite screen capture plugin from Xlib to xcb. I made xcb libs compile required dependency, but availability of X shared memory extension is checked at runtime. It is used to effectively get image pixels data, instead of transfering 8Mb over the wire. Xdamage is used to limit image getting operations only within actually changed rectangles of screen. BUG: 377998 Tested on single-monitor system and dual-monitor, where primary monitor does not start at (0,0) coordinate. Image transfer works fine. Dual-monitor only has problems with receiving mouse cursor position and clicks, but this should be fixed outside of framebuffer plugin. Differential Revision: https://phabricator.kde.org/D5211
2017-06-15 23:20:48 +02:00
*/
#include "xcb_framebufferplugin.h"
#include "xcb_framebuffer.h"
#include <KPluginFactory>
Encode supported platforms in the plugin metdata This way we don't load pipewire on X, or xcb on Wayland regardless if they are configured as preferred or not.
2023-01-18 15:13:42 +01:00
K_PLUGIN_CLASS_WITH_JSON(XCBFrameBufferPlugin, "xcb.json")
Implement XCB framebuffer plugin (port from x11) Previously used x11 plugin does not compile with Qt5, because Qt5 does not use Xlib, it uses xcb. Rewrite screen capture plugin from Xlib to xcb. I made xcb libs compile required dependency, but availability of X shared memory extension is checked at runtime. It is used to effectively get image pixels data, instead of transfering 8Mb over the wire. Xdamage is used to limit image getting operations only within actually changed rectangles of screen. BUG: 377998 Tested on single-monitor system and dual-monitor, where primary monitor does not start at (0,0) coordinate. Image transfer works fine. Dual-monitor only has problems with receiving mouse cursor position and clicks, but this should be fixed outside of framebuffer plugin. Differential Revision: https://phabricator.kde.org/D5211
2017-06-15 23:20:48 +02:00
XCBFrameBufferPlugin::XCBFrameBufferPlugin(QObject *parent, const QVariantList &args)
: FrameBufferPlugin(parent, args)
{
}
Don't pass unused window ids around The wid is only relevant for the xcb framebuffer We can just query it there, no need to pass it around everywhere
2022-08-03 22:00:16 +02:00
FrameBuffer *XCBFrameBufferPlugin::frameBuffer(const QVariantMap &args)
Implement XCB framebuffer plugin (port from x11) Previously used x11 plugin does not compile with Qt5, because Qt5 does not use Xlib, it uses xcb. Rewrite screen capture plugin from Xlib to xcb. I made xcb libs compile required dependency, but availability of X shared memory extension is checked at runtime. It is used to effectively get image pixels data, instead of transfering 8Mb over the wire. Xdamage is used to limit image getting operations only within actually changed rectangles of screen. BUG: 377998 Tested on single-monitor system and dual-monitor, where primary monitor does not start at (0,0) coordinate. Image transfer works fine. Dual-monitor only has problems with receiving mouse cursor position and clicks, but this should be fixed outside of framebuffer plugin. Differential Revision: https://phabricator.kde.org/D5211
2017-06-15 23:20:48 +02:00
{
Allow passing plugin backends some arguments WId is irrelevant on Wayland and it doesn't fully describe everything we might be doing, we can pass a variant map to make sure all necessary information is provided.
2021-10-14 15:53:33 +02:00
Q_UNUSED(args);
Don't pass unused window ids around The wid is only relevant for the xcb framebuffer We can just query it there, no need to pass it around everywhere
2022-08-03 22:00:16 +02:00
return new XCBFrameBuffer;
Implement XCB framebuffer plugin (port from x11) Previously used x11 plugin does not compile with Qt5, because Qt5 does not use Xlib, it uses xcb. Rewrite screen capture plugin from Xlib to xcb. I made xcb libs compile required dependency, but availability of X shared memory extension is checked at runtime. It is used to effectively get image pixels data, instead of transfering 8Mb over the wire. Xdamage is used to limit image getting operations only within actually changed rectangles of screen. BUG: 377998 Tested on single-monitor system and dual-monitor, where primary monitor does not start at (0,0) coordinate. Image transfer works fine. Dual-monitor only has problems with receiving mouse cursor position and clicks, but this should be fixed outside of framebuffer plugin. Differential Revision: https://phabricator.kde.org/D5211
2017-06-15 23:20:48 +02:00
}
#include "xcb_framebufferplugin.moc"
Reference in New Issue Copy Permalink