| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Change-Id: Ieb65b66f28986845f50647ae338678f0a1e7a153
Reviewed-by: Pier Luigi Fiorini <pierluigi.fiorini@gmail.com>
Reviewed-by: Erik Larsson <erik@ortogonal.com>
Reviewed-by: Johan Helsing <johan.helsing@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
This is an optimisation property which can be set on a view. If you have
two views for a surface, then the frontBuffer will be released first
when the last view has released the frontBuffer. With this option all
views with this option set to true will discard the frontBuffer when the
throtlingView discards its frontbuffer
Change-Id: Id628ec60830549ea930c1fff950501de2b073e48
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
This involves removing:
- pickView and mapView from QWaylandOutput
- requestedPos[X,Y] from QWaylandView
Change-Id: Ie53eef434ac6ae7d0d5474f649f78a59ae857167
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>
|
| |
|
|
|
|
|
| |
enable building QtWaylandCompositor by default
Change-Id: I7cf34052b304ca9fef55b7e30ef6a6367b5d75f1
Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>
|
| |
|
|
|
|
|
| |
This will be convenient if there is a view which copies the
currentBuffer to a cache and then wants to release the ref to the buffer
Change-Id: I0b7bbb4bc22c420fdf0d1af4bb1bbf0a4f888bc8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This finaly ties together how to use QWaylandQuickItems with different
shells
It was required to decouple QWaylandView from the QWaylandQuickItem
since QML doesn't play to well with muliple inheritance. The
QWaylandQuickItem can be retrieved from the QWaylandView which is now
conveniently a QObject. Also the QWaylandQuickItem owns the
QWaylandView. This architecture also leaves room for creating a
QWaylandWidget :)
Change-Id: Ib8a00e6f17f0f1bfc3ff244753f021c76db22cb1
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is the views that belong to outputs.
This leads to a couple of interesting cases with enter and leave events,
but the implementation says you will get enter events for the first view
of a surface entering an output, and for the last view being removed
from an output.
Also to throttle a surface, there has to be 1 surface which takes care
of this. This is because if multiple views throttle, then the client
might render to quick.
Change-Id: If4bba380fd4d7f506fd769606cbdea4ce58b908d
|
| |
|
|
| |
Change-Id: Ie5d8899157d77f83f2cf65f236d534b972aa4770
|
|
|
and rename QWaylandSurfaceItem to QWaylandQuickView
Change-Id: I989b482eb79df06e9f265bc2b0ef6b3dce7509d6
|
