GitLab

This is a convenience to allow renderers to figure out the sample
count for their pso by just querying renderTarget()->sampleCount()
where the render target is set up and provided from another component
outside of the renderer's knowledge and control.

These may be used by Q3DS for HDR images (IBL).

do not reimplement the same logic that is already there in
qopenglfunctions.cpp

...so that setting QRhiSwapChain::sRGB behaves identically between
all 4 backends.

The order is important here, if there are multiple operations
targeting or reading from the same texture.

Inspired by QObject::deleteLater()...

...and add a semi-format that can be used to port code with the
'if modernGL then GL_R8 else GL_ALPHA' pattern (in order to support GLES
2.0).

...which comes handy to avoid problems of alloc, destroy, alloc
-> same address as before.

the non-rgba8 formats are a todo for now

To help dealing with ancient GLES 2.0 implementations.

Playing with NoVSync on the additional windows is nice
but does not change much in practice. On Metal it's still
all bad regardless, for instance.

Shader resources are now set via a dedicated API (setShaderResources)
instead of setGraphicsPipeline.

Also extend docs about command buffers and defered command execution.

Do a little cleanup for gl and d3d when it comes to the "fake" command
queues.

sigh

Because we do not currently deal with this on d3d11.

Complements isYUpInFramebuffer().

For instance the Qt Quick renderer will want the Batchable variant for
a vertex shader when rendering merged batches. Make it possible to
communicate this to the backends.

beginFrame() has no applicable flags as of now but the flags parameter is
there for future use.

Sharable resources, which are at least buffers and textures, can now be
orphaned, meaning the owning QRhi can be destroyed before releasing the
QRhiResource. They will still function in a limited way (cannot be rebuilt
anymore) as long as there is at least one QRhi associated with the
QRhiResourceSharingHost (i.e. as long as the share group is non-empty).

...in order to reduce code duplication.

The threaded case cannot be supported on all backends for now.
Revert parts of the previous d3d patch.

Some day we may consider exploring the possibility of doing something
with deferred contexts on d3d11 but that's not an option for now.