« Main differences between V1.7 and V1.8 » : différence entre les versions
Aller à la navigation
Aller à la recherche
Aucun résumé des modifications |
Aucun résumé des modifications |
||
| Ligne 7 : | Ligne 7 : | ||
== Complex status management == | == Complex status management == | ||
Thanks to the <font color=#4169E1>setForcedStatus()</font> method, it is now possible to manage more complex status as above several entries as explained in this [[http://genius.cnes.fr/index.php/Validity_controls# | Thanks to the <font color=#4169E1>setForcedStatus()</font> method, it is now possible to manage more complex status as above several entries as explained in this [[http://genius.cnes.fr/index.php/Validity_controls#Complex_status_management topic]]. | ||
== Absolute path for condensed status == | == Absolute path for condensed status == | ||
When managing error/warning status, it is now possible to get directly the absolute path of a data using the getPathInConfigFile() method (see [[http://genius.cnes.fr/index.php/Validity_controls#Status_management topic]]). | When managing error/warning status, it is now possible to get directly the absolute path of a data using the getPathInConfigFile() method (see [[http://genius.cnes.fr/index.php/Validity_controls#Status_management topic]]). | ||
Version du 26 septembre 2018 à 13:46
Some interesting evolutions and corrections have been implemented in this version. No incompatibilities has been identified versus V1.7 source code .
Clear constraints
It is now possible to reset constraints of a widget using the clearConstraint(), clearInnerDescendantConstraint(), clearAllInnerDescendantConstraint() methods.
Complex status management
Thanks to the setForcedStatus() method, it is now possible to manage more complex status as above several entries as explained in this [topic].
Absolute path for condensed status
When managing error/warning status, it is now possible to get directly the absolute path of a data using the getPathInConfigFile() method (see [topic]).