Fix to method setDumpPython(). Previous implementation allowed only to SET "DumpPtho...

It fixes the following bug: when Dump Python is called first with checked, and after that - with unchecked "Save GUI State" checkbox -- the Python script is written with errors as IParameters has internal "DympPython" property set ON (left from the first call).  Currently, it is possible to set it OFF, and it is done in SalomeApp_Application::OnDumpPython() function.

diff --git a/src/SALOMEDS/SALOMEDS_IParameters.cxx b/src/SALOMEDS/SALOMEDS_IParameters.cxx
index 6540d9feecb20fd0826f0e8e7d996883093578ef..8bc7ed09f181642e24033ab9c29d005e96aa52a3 100644 (file)
--- a/src/SALOMEDS/SALOMEDS_IParameters.cxx
+++ b/src/SALOMEDS/SALOMEDS_IParameters.cxx
@@ -255,7 +255,7 @@ void SALOMEDS_IParameters::setDumpPython(_PTR(Study) study, const string& theID)
   else anID = theID;
 
   _PTR(AttributeParameter) ap = study->GetCommonParameters(anID, 0);
-  ap->SetBool(_AP_DUMP_PYTHON_, true);
+  ap->SetBool(_AP_DUMP_PYTHON_, !isDumpPython(study, theID));
 }
 
 bool SALOMEDS_IParameters::isDumpPython(_PTR(Study) study, const string& theID)