So far not all v5 features were implemented because most of them are
optional. But given that XWayland needs axis_discrete event maybe it's
time to implement them.
CCBUG: 404152
davidedmundson |
KWin |
So far not all v5 features were implemented because most of them are
optional. But given that XWayland needs axis_discrete event maybe it's
time to implement them.
CCBUG: 404152
Lint OK |
No Unit Test Coverage |
Buildable 8280 | |
Build 8298: arc lint + arc unit |
@davidedmundson Would it make sense to have something like
void pointerAxisV5(Qt::Orientations orientations, const QPointF &delta, const QPoint &discreteDelta, PointerAxisSource source);
so we could send a diagonal scroll motion in one frame?
so we could send a diagonal scroll motion in one frame?
We have this for a few things, such as clicking and moving.
IMHO we should make frame() explicitly sent from the caller.
I've hit this a few times (mostly wl_output) where KWayland tries to make things "easy" but in practice ends up making it harder to follow the protocol accurately.
Hard to add retroactively in KF5 though :/
Yeah, I'd prefer this way as well to be honest...
Hard to add retroactively in KF5 though :/
So, it would be KF6 stuff, right?