Salome HOME
Fix for the issue #910: never fully remove the results, just make them disabled when...
authormpv <mpv@opencascade.com>
Thu, 10 Sep 2015 09:33:25 +0000 (12:33 +0300)
committermpv <mpv@opencascade.com>
Thu, 10 Sep 2015 09:33:25 +0000 (12:33 +0300)
src/ModelAPI/ModelAPI_Feature.cpp

index 84fe978475d087f4d62f74d8567caad94a040176..f677d5c52e2a542bc87226141944c271e7909692 100644 (file)
@@ -104,12 +104,12 @@ void ModelAPI_Feature::removeResults(const int theSinceIndex, const bool theFlus
   while( aNextIter != myResults.end()) {
     aGroup = (*aNextIter)->groupName();
     // remove previously erased results: to enable later if needed only actual (of history change)
-    if (theSinceIndex == 0 && (*aNextIter)->isDisabled()) {
-      aNextIter = myResults.erase(aNextIter);
-    } else {
+    //if (theSinceIndex == 0 && (*aNextIter)->isDisabled()) {
+    //  aNextIter = myResults.erase(aNextIter);
+    //} else {
       (*aNextIter)->setDisabled(*aNextIter, true); // just disable results
       aNextIter++;
-    }
+    //}
   }
   if (!aGroup.empty() && theFlush) {
     // flush visualisation changes