Yeah, I can't see why this exists.

Investigation done: It's not

It's technically different to before. The old code had half a small margin each side.

I'm going to ship this as it fixes an easy to hit bug that is definitely wrong.
I'm not trying to ingore any other proposals, we can always expand and change.

Lets fix KIdleTime instead.

A FOSDEM meeting said we would try and create a common generator which will ship with systemd

Done

workspace changes required as a result of a frameworks change raises questions

Code wise, no objections. Needs vdg to approve visual changes.

From a code pov. +1

Marking as needs changes RE: vlad's comment

I'm happy with the model.

Urgh, we should have spotted that at review. Ship it!

This would also be loaded and operational when running in a gnome session. It's important we don't cause issues there.

From a technical POV, pics get copied when selected, so you can do whatever without any user breakage.

Yes

Cool, as long as there's some original source I'm happy

which doesn't seem to have a wayland protocol correspondence

oh, then kill it

I dunno, what is it?

Hello symlink my old friend...

Feedback from some testing:

• we're adding the same tool a bunch of times when a new client is created
• sometimes we fail to enter the surface leaving the cursor "stuck" (with gtk3-demo)

QAbstractSortFilterProxyModel has docs that say you need it, but QSortFilterProxyModel which you inherit from does reset the model in setSourceModel.

If you run /usr/bin/my-kinfocenter you wouldn't spawn this executable in the first place

I can't do that, someone else need to commit it.

Well identified, it is racey.

The detailed description makes sense and VDG people say it's better..

Change is now purely visual, so VDG can have say on the details.

You know my thoughts on per project rules.
But maybe it is different for kwin. Use of setRight() is the easier call than left+width() if you are actually using it for painting and need to think about the 1px the other way round.