This document describes the changes introduced with libkdegames v5, which first appeared in the KDE 4.9 release.
Also, multiple new components have been added which replace existing components. These can be identified by the common class name prefix "Kg". See Reworked components for details.
KGameDifficulty has been replaced by the KgDifficulty and KgDifficultyLevel classes. KgDifficulty stores the current level by itself, and allows for multiple KgDifficulty instances at the same time, although a singleton is provided by the Kg::difficulty() function. The following table shows how to port common uses of KGameDifficulty to this singleton:
|Replace this...||...by this||Comment|
|KGameDifficulty::Medium etc.||KgDifficultyLevel::Medium etc.|
|KGameDifficulty::addStandardLevel(level)||Kg::difficulty()->addStandardLevel(level)||As a convenience, consider to use the new addStandardLevelRange() method.|
(window, receiver, slot)
|Change the slot to the new signature. The old signature contained a standard level argument: Use the "standardLevel" property of the new argument instead.|
|KGameDifficulty::setLevel(level)||Kg::difficulty()->select(level)||If used to restore the selected difficulty from the config file, delete the whole call and your custom config key. KgDifficulty remembers the level selection by itself. Please refer to the APIDOX for details, e.g. how to specify a default difficulty for the first run.|
etc. while setting up a KScoreDialog
|dialog->initFromDifficulty(Kg::difficulty());||If you need the QMaps from these KGameDifficulty functions, you can construct them by iterating over the KgDifficultyLevels. levelWeights maps hardness->key and localizedLevelStrings maps key->title.|
|KGameDifficulty::setRestartOnChange(roc)||Kg::difficulty()->setGameRunning(roc && running)||These two properties of KGameDifficulty are redundant: If both are true, the user will be asked for confirmation before the level is changed. If you do not want this, just do not use the setGameRunning method.|
|KGameDifficulty::setEnabled()||Kg::difficulty()->setEditable()||The property has been renamed to clarify its purpose.|
KGameTheme has been replaced by the KgTheme and KgThemeProvider classes, which generalize its behavior, overcome several hardcoded assumptions and offer some additional convenience.
KGameTheme implicitly looks for themes in KStandardDirs::locate("appdata", "themes"). KgTheme expects you to discover themes with a KgThemeProvider. The following mimics the old KGameTheme behavior:
KgThemeProvider* provider = new KgThemeProvider(QByteArray(), parent); provider.discoverThemes("appdata", QLatin1String("themes"));
If you want to use KgThemeProvider's functionality to automatically save the selected theme, give a non-empty value in the first parameter (see documentation). The default is "Theme". The following explanations will assume that you use this new functionality.
KGameRenderer's constructor syntax has changed. If you use KGameRenderer, give a KgThemeProvider to it:
//before KGameRenderer renderer("themes/default.desktop"); //after KGameRenderer renderer(provider);
And redirect the setTheme() calls to KgThemeProvider:
//before renderer.setTheme("themes/default.desktop"); //after provider->setCurrentTheme(provider->defaultTheme());
Themes in the context of KgThemeProvider are KgTheme instances, rather than simple strings. The valid instances are usually created with discoverThemes(), and can be retrieved with the themes() method.
The KGameRenderer::themeChanged(QString) signal is replaced by KgThemeProvider::currentThemeChanged(const KgTheme*).
Replace KGameThemeSelector by the new KgThemeSelector class.
//before KGameThemeSelector selector(parent, Settings::self(), KGameThemeSelector::NewStuffEnableDownload); //after KgThemeSelector selector(provider, KgThemeSelector::EnableNewStuffDownload, parent);
If the theme selector is the only page in your KConfigDialog, you can discard the dialog and use KgThemeSelector's stand-alone behavior:
//simple example selector->showAsDialog(); //complex example KStandardGameAction::preferences(selector, SLOT(showAsDialog()), actionCollection());
Just constructing and displaying a KgThemeSelector is enough if you use automatic theme selection saving. Since KgThemeSelector applies selection changes automatically, you need to listen to KgThemeProvider::currentThemeChanged if you need to act on theme changes manually.
Any manual selection saving code can be discarded. Selections in the KgThemeSelector will automatically be saved to the application config file. Since KgThemeProvider always saves in the [KgTheme] config group, you might need to migrate the old configuration key. Refer to the kconf_update documentation for details, or look at the update script for the kdegames module (in the libkdegames source tree).