summaryrefslogtreecommitdiff
path: root/src/plugins/cpptools/cppcodegen_test.cpp
diff options
context:
space:
mode:
authorDaniel Teske <daniel.teske@digia.com>2013-06-11 17:15:21 +0200
committerDaniel Teske <daniel.teske@digia.com>2013-06-11 18:33:11 +0200
commit5a631f251ea4956d1c83d8529aca8fe2b9ceff2a (patch)
tree04290ab197e8b9e531d8bbed88356953ad1d5566 /src/plugins/cpptools/cppcodegen_test.cpp
parente8093a9e59bb23f161e9ebdd771d5a01e61b130b (diff)
downloadqt-creator-5a631f251ea4956d1c83d8529aca8fe2b9ceff2a.tar.gz
Qt4Project::updateRunConfigurations: Do not preserve unconfigured rcs
In 0ce0a053 code was added to ensure that if there is a configured runconfiguration, then it'll be made active. This fixes that code to work more robustly. Consider the case: Two runconfigurations a) custom executable runconfiguration unconfigured (active) b) configured qt4runconfiguration The code in upadteRunConfigurations would put a) into the existingConfigured list since it is active, b) since it fits. Thus the code at the end would not change the active runconfiguration, since existingConfigured.at(0)->isConfigured() would be false. Consider now the same case, but with the reverse order. Now the code makes b) active. The ordering between rcs should not matter. Also consider that in the second case, the next run of updateRunConfigurations will remove the now non active unconfigured runconfiguration. Change-Id: I98291db4eda22e9dae3e493a8f31c7d9bb5420d6 Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Diffstat (limited to 'src/plugins/cpptools/cppcodegen_test.cpp')
0 files changed, 0 insertions, 0 deletions