Changes between Version 302 and Version 303 of ReviewHeuristicLab3.3.0Application

Timestamp:

05/07/10 09:30:18 (14 years ago)

Author:

gkronber

Comment:

added issues with mschart controls

ReviewHeuristicLab3.3.0Application

@@ -95 +95 @@
  * It seems strange now that operators have the property `Breakpoint`. It is more usual to set breakpoints on invocations/calls of operators. Also isn't the engine responsible for breakpoints?
    * swagner: As in HL 3.2 the `Breakpoint` property is implemented in operators and can be changed in the GUI of an `OperatorGraph`. Additionally, I decided to add a checkbox to each operator in order to be able to mark breakpoints there as well (this was not possible in HL 3.2). If an operator is marked as breakpoint, an engine stops its execution after this operator has been processed. I agree that it would be more intuitive to store it in some other location, which operators are currently breakpoints. However, I do not immediately know where. Any suggestions?
-
+ * Min selection granularity for zooming should be 1 for the x-axis in `SymbolicRegressionSolutionLineChartView`
+ * Min selection granularity for the x-axis should be adapted to the range of displayed values in all line charts and scatter plots. 
 
 === Priority: LOW ===