Fix QSettings default paths not being initialized when setPath() is called

This only coincidently worked on Linux, because it creates a QSettings
object to read system settings before any user data was executed, thus
initializing the static default path data. However, if only the
SystemPath was modified, the UserPath never got initialized on
non-Linux platforms, causing settings for the users below $PWD.

Also, it removes unncessary checks and mutex locks, which should
give a slight speed up.

Reviewed-By: dt

0 files changed, 0 insertions, 0 deletions