Commit Graph

6 Commits

Author SHA1 Message Date
Laszlo Agocs e32d335c8f sg: Fix culling in layers
Pick-to: 6.10 6.9 6.8
Fixes: QTBUG-136611
Change-Id: If2a0a0365ca24360d850ffce98c0bec4a3961976
Reviewed-by: Jonas Karlsson <jonas.karlsson@qt.io>
2025-07-22 14:17:21 +02:00
Tim Blechmann 1dbdcf070f examples: fix unused parameter warning
Change-Id: I6ca097113fb2b3ba0a7ddde251f9068538af986c
Pick-to: 6.7
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
2024-02-14 02:53:46 +00:00
Laszlo Agocs aeb3bd235a Clean up customrendernode example
Make it more consistent with other scenegraph examples, and make it
more compact, in particular when it comes to handling the QRhi
resources (smart pointers are quite useful in this case since they
help dropping a bunch of lines)

Expand the docs.

Pick-to: 6.6 6.6.0
Change-Id: I97bceca7759db9738d34f0fbf7eb29b0ae6e4c0f
Reviewed-by: Christian Strømme <christian.stromme@qt.io>
2023-09-25 09:01:17 +00:00
Kai Köhne 8f1e6aa0ed Examples: Fix license to Commercial or BSD-3-Clause
Pick-to: 6.5 6.6
Change-Id: Ieb1db96846e02c3b93888ed409af82bfb3567c19
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2023-06-26 16:23:24 +02:00
Laszlo Agocs ace43e1db1 Adapt to the RHI API concept
Besides following the header naming changes, make the obvious API
changes that are based on data that is already there but was hidden
previously due to not wanting anything QRhi to shine through in the
public API.

This kind of hiding is no longer needed, even if qrhi.h and similar
still cannot be included from a public header. Forward declarations
are now perfectly fine however.

Task-number: QTBUG-113331
Change-Id: I9a114082cf9218edc487df50956f5793d6b8bdb4
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
2023-05-22 12:08:08 +02:00
Ben Fletcher 7be8566719 scenegraph: Add example for QSGRenderNode based RHI rendering
Add an example to demonstrate RHI rendering in the scenegraph with a
custom QSGRenderNode.  Works for Vulkan/OpenGL/Metal/D3D rendering
directly, and into a layer.

Change-Id: I0333f63fd729312b71e51f5b6376e46f8afe1fe6
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
2022-11-01 10:39:02 -07:00