# Changes between Version 129 and Version 130 of ReviewHeuristicLab3.3.0Application

Ignore:
Timestamp:
04/08/10 22:35:49 (12 years ago)
Comment:

--

### Legend:

Unmodified
 v129 * swagner: In a discussion with maffenze it was decided to address this issue after the release of HeuristicLab 3.3.0. * Adding a ValueParameter in a VariableCreator and selecting a generic type e.g. ItemList fails because no choice can be made on the generic type of the ItemList (ticket #42). * The !OperatorGraphVisualization doesn't respect operator collections (e.g. SequentialSubScopesProcessor) * 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. * The !OperatorGraphVisualization doesn't respect operator collections (e.g. SequentialSubScopesProcessor). * 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. * In TypeSelector filter types that don't have a constructor (like currently PathTSPTour). * swagner: Generally all items should provide a parameterless constructor. I implemented one for PathTSPTour in r3139. * When the TSP importer is used after halting the execution, the engine should be reset * When the TSP importer is used after halting the execution, the engine should be reset. === Priority: MEDIUM === * Saving a problem doesn't remember the filename when saving again * Saving a problem doesn't remember the filename when saving again. * The TSP problem view: * Would be nice to have paste support (e.g. from Excel) in the datagrid of the string convertible matrix view. * In the operator graph chart view: * Some boxes are sometimes placed above the top end of the chart * mkommend: This behavior could not be reproduced in r3176. * Some boxes are sometimes placed above the top end of the chart. * mkommend: This behavior could not be reproduced in r3176. * Top-down layouting would be better instead of left-right for two reasons: 1. The boxes are usually much wider than high and thus a left-right layout makes the graph even longer 2. A top-down graph better fits the paper orientation in a publication * mkommend: This will be implemented with the other changes regarding the layout of the operator graph. 1. The boxes are usually much wider than high and thus a left-right layout makes the graph even longer. 2. A top-down graph better fits the paper orientation in a publication. * mkommend: This will be implemented with the other changes regarding the layout of the operator graph. * Every IDeepCloneable item needs to have a public default constructor. If Activator.CreateInstance in DeepCloneable.Clone is given a second parameter "true", non-public constructors would also be used. * Viewing different result variables (switching between them) is impossible, because the results view is disabled when running the engine. * TypeSelector view: When only one single type is possible (e.g. DoubleData), select that type and auto-close with ok * A problem should inject a variable that indicates its dimensionality (sometimes you want to set values depending on the dimension of the problem) * swagner: See ticket #922. * TypeSelector view: When only one single type is possible (e.g. DoubleData), select that type and auto-close with OK. * 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. * A problem should inject a variable that indicates its dimensionality (sometimes you want to set values depending on the dimension of the problem). * The description in the start page should show the respective icon or menu entry as crop out of a screenshot in the explanation of what to do. * swagner: Added some button images in r3225. * Focus is not removed from a textbox if one clicks anywhere in the "gray" area. * swagner: This is the behavior of Windows Forms. * abeham: I mentioned this because I want to validate the control by clicking out of the text box and thus losing the focus. Maybe this can be achieved by allowing focus on the control or form. I think by default the "gray area" doesn't accept focus. * abeham: I mentioned this because I want to validate the control by clicking out of the text box and thus losing the focus. Maybe this can be achieved by allowing focus on the control or form. I think by default the "gray area" doesn't accept focus. * There should be a nicer way of saying the chart controls are not installed instead of an exception. * swagner: The HeuristicLab setup will check if the Microsoft Chart Controls are installed and will show a meaningful error message. * The button for changing the evaluation in the TSP view features "+" which is used for adding, not setting in other views. * swagner: In a discussion with maffenze it was decided to use the "+" icon for adding and for setting values as long as there is no better idea which icon to use for setting values. * abeham: I'd suggest EditTable for change operations. Also in the results collection, I'd like to see different icons for DataTable and the solution visualization so that they pop out. I'd suggest Object, or if it hasn't been used already Properties. * abeham: I'd suggest EditTable for change operations. Also in the results collection, I'd like to see different icons for DataTable and the solution visualization so that they pop out. I'd suggest Object, or if it hasn't been used already Properties. * The quality chart looks great! * We should probably use the same colors we had in 1.1 for best/average/worst qualities. * Would be good to be able to hide certain lines. * At some point we'll certainly need export to png,eps functionality (would be great to be able to specify resolution and width/height). * At some point we'll certainly need export to png, eps, etc. functionality (would be great to be able to specify resolution and width/height). * The tooltips should not exceed a certain width. With a long description you've got one line running over the whole screen. * swagner: It is not possible to define a maximum text width and to enforce word wrapping for tool tips. Therefore line breaks have to be set for each tool tip text individually. Please specify which tool tips are too long so that appropriate line breaks can be added. * Going through the scopes with the arrow keys doesn't update the details view of the scope. * Resetting the engine doesn't update the global scope details view (user defined algorithm). * TypeSelector view: Focus should be in the search field when opening it the first time * abeham: Actually I like it on the ok button, but also because it's a fast way of auto-oking those single option cases (see above) * VariableCreator throws an exception when injecting a variable whose value is null * VariableCreator throws an exception when injecting a variable whose value is null. * The view host icon should act like a button that when single-clicked opens the context-menu, when hovering over it, there should be a frame around it like a button so that it's clear that it can be clicked. * swagner: When hovering over the view host icon a tool tip is displayed that explains how the different views can be selected. * abeham: I'm still not fully happy with the view host icon, but it's probably the least priority thing right now * abeham: I'm still not fully happy with the view host icon, but it's probably the least priority thing right now * Some operators have a Parameter "!CurrentScope" that cannot be changed in any way, is there a necessity to display this parameter? * swagner: The scope parameter "!CurrentScope" indicates that the current scope (i.e. its sub-scopes) is manipulated by an operator. It is shown in order to give the user comprehensive information about what an operator does. Maybe this is not really helpful. Should I remove scope parameters in general? In the code of an operator they are not really required, as the current scope can always be accessed via the current execution context. * swagner: In a discussion with maffenze it was decided to keep scope parameters. * abeham: I think more parameter are just more confusing and description of the internal mechanisms of an operator are better displayed in the description text. I'll vote for removal of the current scope parameters, but I'll move this to low priority for now. * Improve description of !SearchIntervalFactor in BreederGeneticAlgorithmManipulator * abeham: I think more parameter are just more confusing and description of the internal mechanisms of an operator are better displayed in the description text. I'll vote for removal of the current scope parameters, but I'll move this to low priority for now. * Improve description of !SearchIntervalFactor in BreederGeneticAlgorithmManipulator. * EvolutionStrategy: * Add parameter to ES to indicate if 1/5 success rule or sigma-self adapation should be used * Add parameter to ES to indicate if 1/5 success rule or sigma-self adapation should be used. ----