Fix to method onDumpPython().

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/SalomeApp/SalomeApp_Application.cxx b/src/SalomeApp/SalomeApp_Application.cxx
index c75f9867f97847545baad4e534f29520f3f875d2..12dfcd7829b4b1e6d81cfebf1dc02009f7e75d0b 100644 (file)
--- a/src/SalomeApp/SalomeApp_Application.cxx
+++ b/src/SalomeApp/SalomeApp_Application.cxx
@@ -530,9 +530,10 @@ void SalomeApp_Application::onDumpStudy( )
   if ( !aFileName.isEmpty() ) {
     QFileInfo aFileInfo(aFileName);
     int savePoint;
+    _PTR(AttributeParameter) ap;
+    _PTR(IParameters) ip = ClientFactory::getIParameters(ap);
+    if(ip->isDumpPython(appStudy->studyDS())) ip->setDumpPython(appStudy->studyDS()); //Unset DumpPython flag.
     if ( toSaveGUI ) { //SRN: Store a visual state of the study at the save point for DumpStudy method
-      _PTR(AttributeParameter) ap;
-      _PTR(IParameters) ip = ClientFactory::getIParameters(ap);
       ip->setDumpPython(appStudy->studyDS());
       savePoint = SalomeApp_VisualState( this ).storeState(); //SRN: create a temporary save point      
     }