summaryrefslogtreecommitdiffstats
path: root/src/widgets/dialogs/qsidebar_p.h
diff options
context:
space:
mode:
authorShawn Rutledge <shawn.rutledge@digia.com>2016-01-06 09:44:11 +0100
committerShawn Rutledge <shawn.rutledge@theqtcompany.com>2016-01-18 08:32:59 +0000
commitb30ea419450c968c009ddcae964b1b54755f11ac (patch)
tree59b786af8f480b4776e1127c75db328b57ba78f9 /src/widgets/dialogs/qsidebar_p.h
parent89f9f7cbdfd085c3536304ae52b8935096db7217 (diff)
eglfs: use QGenericUnixTheme if requested
We need to have reasonable paths for loading icons and such things, just as in any other Unix GUI environment. However there is some concern that it would be too much of a behavior change if there was a theme by default, so for now it's required to set the env var: QT_QPA_PLATFORMTHEME=generic That works because QGuiApplicationPrivate::createPlatformIntegration() reads the env variable and passes platformThemeName to init_platform(). Step 3 in init_platform() does not find a theme plugin by that name (because QGenericUnixTheme is statically linked via libQt5PlatformSupport.a). Then in step 4 it iterates the given platformThemeName plus any which were returned from QPlatformIntegration::themeNames() (which in our case will be an empty list) and calls createPlatformTheme() with each of those, until something is returned. So, QEglFSIntegration::createPlatformTheme() will be called with the value of the QT_QPA_PLATFORMTHEME env var, and QGenericUnixTheme::createUnixTheme() will create the generic, KDE or Gnome theme depending on that value. Change-Id: Id16b881819ba872830b019ab147b32fbc2156520 Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
Diffstat (limited to 'src/widgets/dialogs/qsidebar_p.h')
0 files changed, 0 insertions, 0 deletions