30e27328e3
With OpenGL a scissor (or viewport) rectangle is not allowed to have a negative width or height. Everything else is allowed. This is also the semantic we wish to keep for QRhiViewport and QRhiScissor. This raises some problems. For instance, when we do bottom-left - top-left rectangle conversion, the case of partially out of bounds rects needs to be taken into account. Otherwise, Qt Quick ends up in wrong scissoring in certain cases, typically when the QQuickWindow size is decreased so the content does not fit because that will then start generating negative x, y scissors for clipping (which is perfectly valid but the QRhi backends need to be able to deal with it) Then there is the problem of having to clamp width and height carefully, because some validation layers for some APIs will reject a viewport or scissor with partially out of bounds rectangles. To verify all this, add a new manual test, based on the cubemap one. (cubemap was chosen because that is an ideal test scene as it fills the viewport completely, and so it is visually straightforward when a scissor rectangle is moving around over it) Fixes: QTBUG-78702 Change-Id: I60614836432ea9934fc0dbd0ac7e88931f476542 Reviewed-by: Christian Strømme <christian.stromme@qt.io>
27 lines
463 B
Prolog
27 lines
463 B
Prolog
TEMPLATE = subdirs
|
|
|
|
SUBDIRS += \
|
|
hellominimalcrossgfxtriangle \
|
|
compressedtexture_bc1 \
|
|
compressedtexture_bc1_subupload \
|
|
texuploads \
|
|
msaatexture \
|
|
msaarenderbuffer \
|
|
cubemap \
|
|
cubemap_scissor \
|
|
multiwindow \
|
|
multiwindow_threaded \
|
|
triquadcube \
|
|
offscreen \
|
|
floattexture \
|
|
mrt \
|
|
shadowmap \
|
|
computebuffer \
|
|
computeimage \
|
|
instancing
|
|
|
|
qtConfig(widgets) {
|
|
SUBDIRS += \
|
|
qrhiprof
|
|
}
|