The problem here is that QSettings doesn't build the path in the same way all others APIs do. The folders constructed based on applicationName/organisationName are different.
State saving uses QSettings like this, passing the name to the constructor:
new QSettings(UCApplication::instance().applicationName())
The problem here is that QSettings doesn't build the path in the same way all others APIs do. The folders constructed based on applicationName /organisationNa me are different.
State saving uses QSettings like this, passing the name to the constructor:
new QSettings( UCApplication: :instance( ).applicationNa me())