Main differences between V1.3 and V1.4.1

Some interesting evolutions exist between the V1.4 version and the V1.3 version. Only some incompatibilities exist on the code source but are very easy to correct.

Possibility to hide items in GComponentList

OpenClose arrows appear now to be able to hide widgets in a GComponentList if multiple mode has been chosen.

Global management of the validity status

Now, thanks to the GCondensedStatusInterface it is possible to get the global status (OK, WARNING, ERROR) of a set of data. This mechanism also allows to get the list of the data positionned as WARNING/ERROR. More details are given in the validity controls section.

Possibility to manage missing data in XML files

Now it is possible to read XML data files with missing data. these ones will be replaced by default values. More details are given in the GReadWrite interface and data files management section.

Specific warning for integer entry

In the previous versions, when a user tried to enter something different as a digit in an integer field, no message appeared. For example, entering 123x45 would be the same as 12345. Problems may occured when a user would enter a real value in an integer field (as may be, he did not know it was an integer field) : for example 123.45 will give 12345 without any message. Now, only in case of "." or "e" input, a message will be sent to the user.

Optimized display of real values

Thanks to some feedback when using previous versions, it has been decided to display only 14 digits (rather than 15). Moreover the size of the input field has been enlarged.

At last, a mechanism has been implemented to automatically switch on scientific format when necessary. For example, rather than to display 0.0000000000123456789, we will get now 1.23456789E-11.

Interval validity values display

Now the values are displayed in the same unit as the one chosen (and no more in SI unit as in the previous version). The real format also corresponds to the one used (see just above about optimized display of real values).

More possibilities when using the GFreeChartXY widget

See the corresponding Javadoc at GFreeChartXY

=> incompatibility in the code.

Colors for not enabled fields

The background and foreground colors of "not enabled" fields have been changed in order to be more readable.

Creation of the GBufferedTextArea

Using GTextArea or GConsole may imply some problems when too many informations are stored in such widgets. A GBufferedTextArea has been created in order to better managed it with pagination functionnalities.

But in order to get something consistent between GTextArea, GConsole and GBufferedTextArea, constructors have been slightly changed implying some incompatibility in the code.

Anomaly corrections

Besides these evolutions, some anomalies have been corrected. The main ones are :

 * possibility to use setConstraint for a widget family (same class) of a GPanel
 * Anomalies for some display of the GPlotPanel widget
 * Layout management for the GOpenCloseButton widget

Class constraints

In the previous version, an anomaly has been raised for managing constraints for all widgets of the same type inside a higher level widget (as a GPanel for example). Now, this anomaly has been corrected but the name of the method is now setClassConstraint rather than setConstraint.

=> incompatibility in the code.

Package refactoring

Some refactoring will have to be done due to modification of some classes versus packages location. A "Ctrl-Shift-o" with Eclipse will be sufficient !

=> incompatibility in the code.

Return to the introduction ↑