Details
-
Bug
-
Resolution: Duplicate
-
P2: Important
-
None
-
Qt Creator 3.0.0-rc1
-
None
Description
Some developers are starts multiple QtCreator IDEs without explicitly specifying the '-settingspath' option.
If they do so and the modify some settings e.g. Kits, QtVersion, ... then the settings gets inconsistent and of course could not be correctly read when reading them on next QtCreator start.
As a solution, it would be good to have QtCreator to 'lock' the settings directory during the run of QtCreator. Or at least warn a developer, that the QtCreator settings folder is shared and it may have some implications.
Attachments
Issue Links
- is duplicated by
-
QTCREATORBUG-17373 After running 4.2RC1 4.0.3 has problems
-
- Closed
-
- relates to
-
QTCREATORBUG-20152 Use SettingsAccessor for CMake settings
-
- Closed
-
-
QTCREATORBUG-18110 Some settings are missing per-project configuration
-
- Open
-