# Changes between Version 461 and Version 462 of ReviewHeuristicLab3.3.0Application

Ignore:
Timestamp:
06/28/10 13:55:49 (9 years ago)
Comment:

--

Unmodified
Added
Removed
Modified
• ## ReviewHeuristicLab3.3.0Application

 v461 * Sometimes the arrow is not drawn when connecting two operators, or it's drawn wrong. * The red square surrounding a port still remains selected sometimes after creating a connection. * mkommend: Moved to ticket #1060. * Operator graph tree-view: * The breakpoint icon looks a bit big. * mkommend: This is the default behavior of the Netron library. As far as I understand the source it is related to selection of grouped / stacked items. * abeham: If that means it's impossible to change please delete the whole issue. I'm moving it down in the priority list. * mkommend: Moved to ticket #1060. * Placing two operators in the operator graph view above each other and left-clicking selects the operator on top, but right-clicking opens the context menu on the bottom one * mkommend: Moved to ticket #1060. * When removing the initial operator in a user defined algorithm the solve button is still enabled (there is no exception) * I create a batch run, produce some runs, clear the runs and save the batch run. When I load it again and produce some more runs they'll have IDs starting from the last run produced. * I'd like an option to increase/decrease the font size and increase/decrease the arrow strength in the operator graph view. * mkommend: Moved to ticket #1060. === Priority: LOW === * 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. * swagner: In a discussion with maffenze it was decided to address this issue after the release of HeuristicLab 3.3.0. * mkommend: Moved to ticket #1060. * 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. * mkommend: Moved to ticket #1060. * 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. 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. * mkommend: Moved to ticket #1060. * Focus is not removed from a textbox if one clicks anywhere in the "gray" area. * swagner: This is the behavior of Windows Forms. * panning while pressing the middle mouse button would be nice too * display updates while scrolling and panning are rather slow * mkommend: Moved to ticket #1060. === Priority: LOW === === Priority: LOW === * After zooming out in the operator graph visualization multiple times (approx. 50 times) an exception is thrown. ---- * mkommend: Moved to ticket #1060. ----