aboutsummaryrefslogtreecommitdiffstats
path: root/examples/quick/rendercontrol/window_singlethreaded.cpp
Commit message (Collapse)AuthorAgeFilesLines
* examples: replace 'foreach' with 'range for'Anton Kudryavtsev2016-09-031-4/+4
| | | | | | | | While touching the code, replace QStringLiteral with QL1S in QStringBuilder expression. Change-Id: I2519b254d82453e1c9bd5b834c0bd78e5c026f83 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* Don't call render during expose, since we are already calling render().Jan Arve Saether2016-02-051-2/+3
| | | | | | | | | This causes drawing artifacts on Win7 with ANGLES d3d11 backend. Task-number: QTBUG-49923 Change-Id: I801282c4359bd485d1894e409e34393b4264d994 Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
* Port examples to new connection syntax.Friedemann Kleint2015-07-221-1/+1
| | | | | Change-Id: I121c59ac0ad56acb4cd54b99ecd37567368385ce Reviewed-by: Alan Alpert <aalpert@blackberry.com>
* Fix rendercontrol example for screens with different dprLaszlo Agocs2015-04-281-1/+18
| | | | | | | | | | | | | | | | renderWindow() was not reimplemented in the example. This is pretty bad since renderWindowFor() fails to find a window and thus falls back to using the default device pixel ratio (which is the highest dpr present in the system). The result is broken content from Quick because it operates with a dpr of 2 any time a retina screen is connected, even when the example's own QWindow is placed on a normal screen. Add also a note to the QQuickRenderControl docs because it is easy to overlook. Task-number: QTBUG-45613 Change-Id: I31bf92ec285f3d9867a5604a4b4e3bea73791932 Reviewed-by: Gunnar Sletta <gunnar@sletta.org>
* Recreate the FBO on dpr change in rendercontrol exampleLaszlo Agocs2015-04-281-5/+25
| | | | | | | | | Even when the window size is not changing. This provides a useful example of connecting to the screenChanged() signal. Task-number: QTBUG-45613 Change-Id: I0652838d9c0cfec8b64b3422997159f385445b20 Reviewed-by: Gunnar Sletta <gunnar@sletta.org>
* Avoid showing garbage when resizing the rendercontrol exampleLaszlo Agocs2015-04-281-0/+1
| | | | | | | | | | | The threaded variant was working well since that triggers a render when resizing. The single threaded version lacked this and this resulted in showing garbage on OS X at least since the new FBO had undefined contents. Avoid this. Task-number: QTBUG-45613 Change-Id: Ibb3d3f7640bab5da913df1c0c63cc3a3aaafb140 Reviewed-by: Gunnar Sletta <gunnar@sletta.org>
* Fixed license headersJani Heikkinen2015-02-171-3/+3
| | | | | Change-Id: I4d5640ff95e1361ec7e65fb3e87d7726d8185ff5 Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
* Update copyright headersJani Heikkinen2015-02-121-5/+5
| | | | | | | | | Qt copyrights are now in The Qt Company, so we could update the source code headers accordingly. In the same go we should also fix the links to point to qt.io. Change-Id: I61120571787870c0ed17066afb31779b1e6e30e9 Reviewed-by: Iikka Eklund <iikka.eklund@theqtcompany.com>
* Prevent windows outside the gui thread in rendercontrol exampleLaszlo Agocs2015-01-071-3/+3
| | | | | | | | | | | | | | | | In the multithreaded case we attempted to create QWindows outside the gui thread on platforms where QOffscreenSurface is backed by the hidden QWindow in the absence of a better solution. This has to be avoided. Therefore, pass a suitable surface from the gui thread instead. This will avoid "Attempting to create QWindow-based QOffscreenSurface outside the gui thread." type of warnings when running on OS X with --threaded. Change-Id: Ie3ebeeeaa9e6bdf83e763e40213e2940fbfde667 Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@theqtcompany.com> Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>
* rendercontrol example: calculate fbo size correctlyLaszlo Agocs2014-12-181-1/+1
| | | | | Change-Id: Ida1e7cb9426d31ed6406dd6db86f5834f0f1a6ac Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>
* rendercontrol example: Add missing flushesLaszlo Agocs2014-12-171-0/+2
| | | | | | | | Otherwise we will show broken output with some drivers. QQuickWidget does this already. Change-Id: I5193595c4606d0497dbe85f6f8c670618ca366e9 Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>
* Support threading with QQuickRenderControlLaszlo Agocs2014-12-121-0/+273
Reorganize the rendercontrol example to demonstrate both the single and multi threaded approaches. A small helper function is introduced to the QQuickRenderControl API: The QSGRenderContext has to live on the render thread. Previously there was no way for applications to move it to the desired thread. This is now possible. Pass --threaded to the rendercontrol example to use a separate render thread. [ChangeLog][QtQuick] QQuickRenderControl can now be used to render the Qt Quick scene on a dedicated render thread, similarly to how the built-in threaded render loop operates. Task-number: QTBUG-42813 Change-Id: I01c3b2ffca8a174d9d2c267a51f2e484ed7b34b3 Reviewed-by: Gunnar Sletta <gunnar@sletta.org> Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>