summaryrefslogtreecommitdiffstats
path: root/tests/auto/corelib/concurrent/qthreadpool/.gitignore
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@qt.io>2022-11-25 13:54:06 +0100
committerTor Arne Vestbø <tor.arne.vestbo@qt.io>2022-11-26 14:07:23 +0000
commitf32aa06f4f925e9a14db1bf76918358480b98b6a (patch)
treef08548e24c9a16cfe85e1d01104936e76ae108e0 /tests/auto/corelib/concurrent/qthreadpool/.gitignore
parentf0cd18706f6ffca09a7bfbc84542a9e79b4a55f3 (diff)
Windows: Reevaluate dark frames if the application palette changes
Since 5ea7e3a8111b2939f0c91b750aa1c62ab16ab715 we are using dark window frames if the default palette is dark, unless applications explicitly override dark frame support. If the palette changes during runtime, we didn't reevaluate that setting. Do that by handling ApplicationPaletteChange events in QWindowsWindow. We still have to respect an explicit opt-out. Simplify the code at the call sites of setDarkBorder(), we don't need to check all the time whether the application has opted out of dark frame support. Pick-to: 6.4 Task-number: QTBUG-72028 Change-Id: I94e7d33cd21f9656ca210b43e775f487abc25b54 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Diffstat (limited to 'tests/auto/corelib/concurrent/qthreadpool/.gitignore')
0 files changed, 0 insertions, 0 deletions