https://bugs.kde.org/show_bug.cgi?id=295775
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@davidedmundson.co.uk
--- Comment #1 from David Edmundson <k...@davidedmundson.co.uk> ---
To give a status update on this.
We now have support for (nicely!) rendering QtQuick inside an Effect.
The close button is implemented as relatively easy to work with object instead
of a set of hacks and external windows.
EffectFrame also follows the same path (patch in review). It's a clear starting
point.
---
That still leaves the problem of windows, we have two options here:
- Add a QQuickItem subclass that has a window as a texture.
Present windows can just be a fullscreen QtQuick window that shows that.
Challenge is that to do it in the "correct" place in QSG means rendering from
one context to another.
Would be simple if we just shared one common context instead of using a shared
context, but that would require Kwin letting Qt create the main GL context.
Also doing the animation from the current state will be somewhat tricky to get
spot on. It requires the present windows effect going fullscreen and faking the
current state.
- Add a QQuickItem subclass that doesn't draw anything and just manipulates an
EffectWindow
Downside is this kinda means you can only draw a window once, which means we
can't share this path with a regular tabbox.
Also you can't control stacking order with overlays/underlays.
It's still better than the current Tabbox style faux-QQuickItem that overlays
another window as the code will be a lot less spider-y, and it can be
underneath the rendered QML.
--
You are receiving this mail because:
You are watching all bug changes.
