- provide an asset catalog .json file for both Xcode 13 and 14 formats. Apps built against the Xcode 13 SDK are not validated anymore by the App store, but it's still useful to see how things were before. - Xcode 13 required the following icon sizes for a universal iOS app: 60x60@2x, 76x76@2x\~ipad, 167x167, 1024x1024 - Xcode 14 only needs the 1024x1024 one - icons need to be embedded into the asset catalog starting with iOS 11 according to Apple docs (not sure which Xcode version, but it's needed for both Xcode 13 and Xcode 14), and they don't have to manually be copied into the bundle anymore, Xcode takes care of that when processing the asset catalog - add an 167x167 icon image for the iPad pro for Xcode 13 - add an 1024x1024 icon image that is required for successful app store submission and embed it into the asset catalogs - for Xcode 13, we need to manually specify all the required icon sizes - for Xcode 14 we can rely on Xcode to generate the smaller icons from the big one - because the icons need to live in the asset catalog folder, remove unnecessary icons in the appicons folder. - for the cmake project, make sure the asset catalog compiler generates the icons by setting the XCODE_ATTRIBUTE_ASSETCATALOG_COMPILER_APPICON_NAME attribute qmake does automatically already. it would be nice if we can do that automatically in a future Qt version - remove unused icon references in Info.plist file with Xcode 13 - remove all icon references in Info.plist with Xcode 14, rely on Xcode to add that info via its generated partial Info.plist file that gets merged into the main one. - don't include CMakeLists.txt as a text resource Amends cf3535fdf2e7fe52b36aaa4b94a53525fd6640f4 Pick-to: 6.5 Task-number: QTBUG-104519 Task-number: QTBUG-110921 Task-number: QTBUG-116784 Change-Id: I0bc556e66647a66bc21402ea62db3374d0970e97 Reviewed-by: Amir Masoud Abdol <amir.abdol@qt.io> Reviewed-by: Alexey Edelev <alexey.edelev@qt.io> (cherry picked from commit bf2587d9e5a3b25ca6dc1224a635bd8565681d2b)
This directory contains autotests and benchmarks based on Qt Test. In order to run the autotests reliably, you need to configure a desktop to match the test environment that these tests are written for. Linux X11: * The user must be logged in to an active desktop; you can't run the autotests without a valid DISPLAY that allows X11 connections. * The tests are run against a KDE3 or KDE4 desktop. * Window manager uses "click to focus", and not "focus follows mouse". Many tests move the mouse cursor around and expect this to not affect focus and activation. * Disable "click to activate", i.e., when a window is opened, the window manager should automatically activate it (give it input focus) and not wait for the user to click the window.