In D8798#169155, @ngraham wrote:

$ kcmshell5 touchpad
kcm_touchpad: Using X11 backend

The file on disk is at /usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so (on KDE Neon and other Ubuntu-based distros)

unrelated things

Search all frameworks together as components

I wanted to test it, but I'm not sure how to.
kcmshell5 input doesn't give me anything, am I looking at the right place?

Go for it, master branch.

Okay, let's give it a try and see where this takes us.

Yes, this works, the code in question was in SystemTray, it looks just fine there.
Also I've been using Heading in Discover for months and never saw this issue.

It looks a bit odd, I kind of miss some frame around the changelog text. Don't you?

Won't this introduce other usability issues? :/

As discussed

In D8859#168823, @ckertesz wrote:

I worked a half year ago to make the hackish Android build to something more simple and organized inside CMake on Linux desktop environment.
I don't know how the Docker env. differs from Ubuntu Linux, but I don't wanna spend time to figure it out. I invested plenty of time to make it work inside the current CMake build.

IIUC then the changes model will *always* be instantiated, as the project tree view tracks VCS branches to get the branch name of the project(s). Thus the optimization probably no longer makes sense.

What's the crash? This was done so that we weren't monitoring changes if nobody was listening to them.

Added "" around a variable that may contain ;

Pass LANG=C to readelf so it doesn't appear in catalan (or anything other than C) and pass ECM_ADDITIONAL_FIND_ROOT_PATH to look for dependencies

Here's the fork as requested kde:scratch/apol/breeze-video-sddm.

Ping?

Maybe instead of having all of the configuration UI's a better first approach would be to detect the plugins we can use from what's in the repository?

No for the same reason.

❤ I meant to do this for longtime, never did it, thanks Mr @kossebau.

If you're emitting something in the constructor, how could a UI be connected to it?

LGTM

In D8173#167835, @aacid wrote:

In D8173#167776, @apol wrote:

I either need more information

I'm happy to provide any information you want, i just don't know what you need other than KConfigCore.so is in the apk without your patch and not with your patch.

Remove debug variable

I've done a build of with and without and I don't see such differences:

Oops

If we're doing some caching in there now anyway, can we perhaps add individual signals for the margins or is it not worth it?

Improve performance while maintaining output