Marc Mutz ac6e8b3b21 savegame ex.: fix include order [2/2]: game.h ... Includes should be ordered from most specific to most general. This means that project-specific includes always come before Qt includes. This example didn't follow that guideline. Fix. Amends 88e8094f18. Task-number: QTBUG-108857 Pick-to: 6.5 6.4 6.2 5.15 Change-Id: Iafdae9dd8e70ff99882c4344a023a21d15fa3c54 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>		2023-02-08 18:24:17 +01:00
..
doc/src	Link update for Data Input Output in the save game example	2023-01-05 15:22:00 +01:00
CMakeLists.txt	Examples: Use PRIVATE CMake linkage	2022-11-30 14:48:50 +01:00
character.cpp	savegame ex.: use NSDMI, =default the default ctor	2023-02-08 08:37:21 +01:00
character.h	savegame ex.: use NSDMI, =default the default ctor	2023-02-08 08:37:21 +01:00
game.cpp	savegame ex.: use ranged instead of indexed loops	2023-02-08 08:37:21 +01:00
game.h	savegame ex.: fix include order [2/2]: game.h	2023-02-08 18:24:17 +01:00
level.cpp	savegame ex.: use ranged instead of indexed loops	2023-02-08 08:37:21 +01:00
level.h	savegame ex.: make Level ctor explicit	2023-02-08 18:24:16 +01:00
main.cpp	savegame ex.: fix include order	2023-02-08 08:37:21 +01:00
savegame.pro	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00