Changes between Version 202 and Version 203 of ReviewHeuristicLab3.3.0Application
- Timestamp:
- 04/26/10 09:50:28 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReviewHeuristicLab3.3.0Application
v202 v203 6 6 7 7 === Priority: HIGHEST === 8 * Adding a `ValueParameter<T>` in a `VariableCreator` and selecting a generic type e.g. `ItemList<T>` fails because no choice can be made on the generic type of the `ItemList` (ticket #42). 9 * When the TSP importer is used after pausing the execution, the engine should be reset. 8 10 9 11 === Priority: HIGH === … … 11 13 * The flow chart is very nice, but sometimes arrows are a bit wild and going backwards which creates a not so nice strikethrough appearance. Would be good to have non-direct arrows as well. 12 14 * swagner: In a discussion with maffenze it was decided to address this issue after the release of HeuristicLab 3.3.0. 13 * Adding a `ValueParameter<T>` in a `VariableCreator` and selecting a generic type e.g. `ItemList<T>` fails because no choice can be made on the generic type of the `ItemList` (ticket #42).14 15 * The !OperatorGraphVisualization doesn't respect operator collections (e.g. `SequentialSubScopesProcessor`). 15 16 * mkommend: This feature will rarely be used by a standard user and it will not be fixed right now. Although special shapes for `MultipleCallOperators` are planned. 16 17 * In `TypeSelector` filter types that don't have a constructor (like currently `PathTSPTour`). 17 18 * swagner: Generally all items should provide a parameterless constructor. I implemented one for `PathTSPTour` in r3139. 18 * When the TSP importer is used after pausing the execution, the engine should be reset.19 19 * When there is an error in one of the item's constructors, the `TypeSelector` dialog (when pressing the "new" button) will open the first time, but stop listing items after encountering the item with the error. The second time the `TypeSelector` is shown through the "new" button, the optimizer crashes with an exception. 20 20 * A !KeyNotFoundException is thrown in Values_ItemsAdded when a `DataTableView` is closed while it is updated. … … 40 40 * `TypeSelector` view: When only one single type is possible (e.g. `DoubleData`), select that type and auto-close with OK. 41 41 * In a discussion with maffenze it was decided to show the type selector dialog in every case as we fear that it might be irritating for a user, if the dialog is sometimes shown and sometimes not shown. 42 * A problem should inject a variable that indicates its dimensionality (sometimes you want to set values depending on the dimension of the problem).43 * swagner: In a discussion with abeham it was decided that a problem dimension parameter is not really required.44 42 * Adding a new parameter through the GUI and choosing a `ConstrainedValueParameter` does not make sense as the set of valid values cannot be defined anywhere in the GUI. The parameter will never be able to take a value. Additionally, switching the view for this `ConstrainedValueParameter` to a `ValueParameterView` and setting a value there leads to an exception. The `ValueParameterView` should not be a view for the `ConstrainedValueParameter`. 45 43 * Adding a new `ValueParameter<T>` could create a default value if T is instantiable. For most !ValueParameters you will want to have a value upon creation.
