Main differences between V2.1 and V2.1.1 : Différence entre versions

De Wiki
Aller à : navigation, rechercher
(Page créée avec « This version is mainly due to the correction of both anomalies listes below … == == == Anomaly corrections == * Saving displayed orbit as well as the "pivot" referenc... »)
 
(Anomaly corrections)
Ligne 7 : Ligne 7 :
 
* Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed in the previous V2.1 version:
 
* Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed in the previous V2.1 version:
 
** if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
 
** if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
** if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly.
+
** if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly. Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
+
* In the GPIntegrator widget, updating tolerances was not correctly done for "Reduced" mode.
* In the GPIntegrator widget, updating tolérances was not correctly done for "Reduced" mode.
+

Version du 31 octobre 2019 à 09:40

This version is mainly due to the correction of both anomalies listes below …

Anomaly corrections

  • Saving displayed orbit as well as the "pivot" reference is now correctly working. Indeed in the previous V2.1 version:
    • if the user only modified the type of anomaly then saved, this change was not recovered in the saved file. Thus, the next load displayed the original type of anomaly.
    • if the user modified the type of parameters and afterwards changed again the type of anomaly, for display, only the type of parameters was saved and the next load displayed a true anomaly. Note that anyway, even in this new version, when you change the type of parameters, the anomaly is automatically set to "true".
  • In the GPIntegrator widget, updating tolerances was not correctly done for "Reduced" mode.