GitLab

Summary:
There was various threads using the same kconfig[group] at the same time, so bad things happened.
Add a mutex

BUGS: 398416

Test Plan:
Run
  rm -f ~/.config/palapeli* && palapeli
a few times, see it doesn't crash anymore

Reviewers: #kde_games

Subscribers: chehrlic, kde-games-devel

Differential Revision: https://phabricator.kde.org/D16118

Otherwise we're casting an event to class it's not and that's undefined
behaviour

Give m_updateTimer a parent so it's automatically deleted by it when
it's destroyed

Since at TextureHelper::removeScene the scene pointer is already dead,
casting it is undefined behaviour, so what we do to not have to do that
is make the list of scenes just be of qobject * so on remove we don't
have to cast and we juts cast when iterating, solves the undefined
behaviour and doesn't make the code much uglier

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Summary:
When the scene/views are cleared and there is still an interaction active, palapeli will crash.
This happens to due the fact that the interactors are holding pointers to pieces which are cleared
by Scene::clearPieces()
BUG 336075

Test Plan:
As described in the bug description: Create a shortcut for restarting the puzzle, select a piece
and move it around. In the meantime restart the puzzle -> no more crash

Reviewers: #kde_games

Subscribers: #kde_games

Differential Revision: https://phabricator.kde.org/D7637