Both are now using a different instance of the Settings class, in
Core & Project, depending on the settings type

Those variables won't be saved to the preference file.
Private variables are meant to be saved, but must not generate any UI

Loglines now contain thread ID, time, and a severity level marker

Print warning before a possible assertion failure. It was seen that this part of code is reached when a possible assertion is failed. So, better print warning before quiting on an assertion failure.
Signed-off-by: Hugo Beauzée-Luyssen <beauze.h@gmail.com>

Also: QFlag is now used to store flags combination.

Settings are not arbitrarly ordered anymore.

Fixes #56

Fix forward declaration of QXMLStreamReader, breaks on Mac OS; see a discussion here: http://lists.trolltech.com/qt-interest/2008-07/thread00798-0.htmlSigned-off-by: Hugo Beauzée-Luyssen <beauze.h@gmail.com>

We don't have to expose the subsystem that will store the settings.
All that matters is to differenciate project and software settings.

This fixes issue #142

- reenabled save/load
- added a group method, wich will return all the value in a group ( for example,
  keyboard/* )
- added a Qt::ConnectionType to the watchValue method
Signed-off-by: Hugo Beauzee-Luyssen <beauze.h@gmail.com>