it is essentially container for other modules and all but the randr
module are not valid (not maintained as part of Katana)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
by the time ksplash gets the X11 events for startup phases the startup
process is (and should be) done, especially after the display
configuration is done and the monitor is ready to output thus ksplash
does not really indicate much
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it includes the hidden KIO slave, font viewer, font installer, font
manager (enable/disable user or system fonts) and thumbnailer.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the only other way to control which meta information to show in tooltips
and such is to enable Dolphin information panel, find file that has the
desired metadata to disable and right click on the metadata widget after
hovering over the file which is very much not obvious and tedious
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
since kde-runtime was merged into kde-workspace some checks definitions are
duplicated in config-runtime headers thus it is removed.
missing function and header checks were added, most of which also missing in
kde-runtime and kde-workspace so that is by no means mistake made during the
merge.
the check for libkstat for Solaris is actually done via /dev/kstat existence
check from ksysguardd/Solaris/Solaris.cmake.
Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
* move ksplash KCM module to kcontrol sub-directory, ksplash it
build always and there is no reason to keep it out of the
kcontrol directory holding all major KCM modules
* merge some sub-category modules into other major categories
almost the same way it is done in KDE5 as it makes much more
sense and users do not have to go to in-and-out of
sub-categories to configure the overall desktop appearance
- application-appearance -> desktop-appearance
- window-behaviour -> workspace-behavior
- workspace-appearance-and-behavior -> workspace-behaviour
