« Main differences between V1.5 and V1.6 » : différence entre les versions
Aller à la navigation
Aller à la recherche
Aucun résumé des modifications |
Aucun résumé des modifications |
||
| (10 versions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 1 : | Ligne 1 : | ||
Some minor evolutions and corrections have been implemented in this version. No incompatibility has been identified on V1.5 code source. | Some minor evolutions and corrections have been implemented in this version. No incompatibility has been identified on V1.5 code source. | ||
== Creation of the GEntryConstant widget == | |||
This widget is a specific [ | This widget is a specific [{{PathCurrentJavaDoc}}/fr/cnes/genius/highLevel/GEntryConstant.html GEntryConstant] widget offering the display of a dedicated button to get predifined values. It is useful for specific physical "constants" that depend on a model as gravitational term, equatorial radius, etc ... | ||
== Creation of the GStandardApplication widget == | |||
Specific widgets have been created to get a "standard" main application frame (see specific [[ | Specific widgets have been created to get a "standard" main application frame (see specific [[How_to_build_a_standard_application|How to build a Standard Application GUI]] topic) | ||
== Creation of class and methods to build VTS files == | |||
It is now possible to use the objects to create VTS files (ephemeris, attitude and event ones): | It is now possible to use the objects to create VTS files (ephemeris, attitude and event ones): | ||
* [ | * [{{PathCurrentJavaDoc}}/fr/cnes/genius/vts/VTSHeaderInfo.html VTSHeaderInfo] | ||
* [ | * [{{PathCurrentJavaDoc}}/fr/cnes/genius/VTSEPHWrite.html VTSEPHWriter] | ||
* [ | * [{{PathCurrentJavaDoc}}/fr/cnes/genius/vts/VTSATTWrite.html VTSATTWriter] | ||
* [ | * [{{PathCurrentJavaDoc}}/fr/cnes/genius/vts/VTEVETWrite.html VTSEVEWriter] | ||
== Unique GUnit class == | |||
The internal units management has been slightly modified in order not to have specific units for temperatures and percentages. This management also allows to manage consistency between different units (i.e. « km » is consistent with « m »). This functionality is mainly used by the [ | The internal units management has been slightly modified in order not to have specific units for temperatures and percentages. This management also allows to manage consistency between different units (i.e. « km » is consistent with « m »). This functionality is mainly used by the [{{PathCurrentJavaDoc}}/fr/cnes/genius/plots/GPlotPanel.html GPlotPanel] widget. | ||
== Possibility to set the mininimum and maximum amount of elements in GComponentList == | |||
It is now possible to set a minimum and/or maximum values for the size of the list displayed (useful if the widgets are memory consuming and may cause some <font color=#FF8C00>JVM</font> memory error). | It is now possible to set a minimum and/or maximum values for the size of the list displayed (useful if the widgets are memory consuming and may cause some <font color=#FF8C00>JVM</font> memory error). | ||
| Ligne 27 : | Ligne 27 : | ||
=> <font color=#990099>possible compilation error due to the add of an exception when using the</font> <font color=#4169E1>setList()</font> <font color=#990099>method.</font> | => <font color=#990099>possible compilation error due to the add of an exception when using the</font> <font color=#4169E1>setList()</font> <font color=#990099>method.</font> | ||
== Not useful scrollbars in GComponentList == | |||
A side effect of a V1.5 evolution was the fact that, by default, a [ | A side effect of a V1.5 evolution was the fact that, by default, a [{{PathCurrentJavaDoc}}/fr/cnes/genius/lowLevel/GPanel.html GPanel] has its horizontal and vertical scrollbars activated (if needed). As [{{PathCurrentJavaDoc}}/fr/cnes/genius/highLevel/GComponentList.html GComponentList] creates intermediate [{{PathCurrentJavaDoc}}/fr/cnes/genius/lowLevel/GPanel.html GPanel], it ensued a not very ergonomic scrollbar stacking. Now, these intermediate scrollbars do not appear anymore. | ||
== Possibility to get one or several colums data with the getColumns() method of GPlotDataMadonaReader == | |||
In the previous version, this method allowed getting to data columns : one for the abscissae, the other for the ordinates. Now it is possible to get as many columns as possible. | In the previous version, this method allowed getting to data columns : one for the abscissae, the other for the ordinates. Now it is possible to get as many columns as possible. | ||
== Evolution of GCommandLauncher to allow two different GTextArea interfaces (Output & Error) == | |||
Modification of [ | Modification of [{{PathCurrentJavaDoc}}/fr/cnes/genius/threads/GCommandLauncher.html GCommandLauncher] to allow to send <font color=#FF8C00>stdout</font> and <font color=#FF8C00>sterr</font> flows towards two different [{{PathCurrentJavaDoc}}/fr/cnes/genius/lowLevel/GTextAreaInterface.html GTextAreaInterface]. | ||
If only one [ | If only one [{{PathCurrentJavaDoc}}/fr/cnes/genius/lowLevel/GTextAreaInterface.html GTextAreaInterface] is given, both <font color=#FF8C00>stdout</font> and <font color=#FF8C00>sterr</font> will be sent. | ||
== Non recoverable exceptions management == | |||
Some exceptions cannot be directly catched. As an example, in the previous versions, we may raise an exception when we enter a wrong date format in a [http://tu-dctsb-p02.cst.cnes.fr/javadoc/fr/cnes/genius/current/fr/cnes/genius/highLevel/GEntryDate.html GEntryDate] field. The result was displaying a pop up window including the stack trace of the error which is not very ergonomic. Now this sort of pop up windows will not appear but is possible for your application to get it or to have a specific pop up window. A specific tutorial is available in the | Some exceptions cannot be directly catched. As an example, in the previous versions, we may raise an exception when we enter a wrong date format in a [http://tu-dctsb-p02.cst.cnes.fr/javadoc/fr/cnes/genius/current/fr/cnes/genius/highLevel/GEntryDate.html GEntryDate] field. The result was displaying a pop up window including the stack trace of the error which is not very ergonomic. Now this sort of pop up windows will not appear but is possible for your application to get it or to have a specific pop up window. A specific tutorial is available in the [[:Fichier:Genius-1.6-tutorials.zip|Tutorials]]. | ||
== Anomaly corrections == | |||
* Error when reading a date with [{{PathCurrentJavaDoc}}/fr/cnes/genius/plots/GPlotDataMadonaReader.html GPlotDataMadonaReader]: in the previous version, reading a date could occur up to one second error. | |||
* After a copy-paste action on a [{{PathCurrentJavaDoc}}/fr/cnes/genius/highLevel/GTable1D.html GTable1D] widget, the result was a single modified vector with only one modified value and no change on the size of the vector. Moreover, the "*" sign did not appear. | |||
[[WELCOME_TO_THE_GENIUS_WIKI|Return to the introduction ↑]] | [[WELCOME_TO_THE_GENIUS_WIKI|Return to the introduction ↑]] | ||
Dernière version du 10 juillet 2017 à 08:08
Some minor evolutions and corrections have been implemented in this version. No incompatibility has been identified on V1.5 code source.
Creation of the GEntryConstant widget
This widget is a specific GEntryConstant widget offering the display of a dedicated button to get predifined values. It is useful for specific physical "constants" that depend on a model as gravitational term, equatorial radius, etc ...
Creation of the GStandardApplication widget
Specific widgets have been created to get a "standard" main application frame (see specific How to build a Standard Application GUI topic)
Creation of class and methods to build VTS files
It is now possible to use the objects to create VTS files (ephemeris, attitude and event ones):
Unique GUnit class
The internal units management has been slightly modified in order not to have specific units for temperatures and percentages. This management also allows to manage consistency between different units (i.e. « km » is consistent with « m »). This functionality is mainly used by the GPlotPanel widget.
Possibility to set the mininimum and maximum amount of elements in GComponentList
It is now possible to set a minimum and/or maximum values for the size of the list displayed (useful if the widgets are memory consuming and may cause some JVM memory error).
=> possible compilation error due to the add of an exception when using the setList() method.
Not useful scrollbars in GComponentList
A side effect of a V1.5 evolution was the fact that, by default, a GPanel has its horizontal and vertical scrollbars activated (if needed). As GComponentList creates intermediate GPanel, it ensued a not very ergonomic scrollbar stacking. Now, these intermediate scrollbars do not appear anymore.
Possibility to get one or several colums data with the getColumns() method of GPlotDataMadonaReader
In the previous version, this method allowed getting to data columns : one for the abscissae, the other for the ordinates. Now it is possible to get as many columns as possible.
Evolution of GCommandLauncher to allow two different GTextArea interfaces (Output & Error)
Modification of GCommandLauncher to allow to send stdout and sterr flows towards two different GTextAreaInterface. If only one GTextAreaInterface is given, both stdout and sterr will be sent.
Non recoverable exceptions management
Some exceptions cannot be directly catched. As an example, in the previous versions, we may raise an exception when we enter a wrong date format in a GEntryDate field. The result was displaying a pop up window including the stack trace of the error which is not very ergonomic. Now this sort of pop up windows will not appear but is possible for your application to get it or to have a specific pop up window. A specific tutorial is available in the Tutorials.
Anomaly corrections
- Error when reading a date with GPlotDataMadonaReader: in the previous version, reading a date could occur up to one second error.
- After a copy-paste action on a GTable1D widget, the result was a single modified vector with only one modified value and no change on the size of the vector. Moreover, the "*" sign did not appear.