#115 closed enhancement (rejected)
CombinedOperator GUIDs in the scope tree should be invisible
| Reported by: | gkronber | Owned by: | swagner |
|---|---|---|---|
| Priority: | lowest | Milestone: | HeuristicLab 3.3.0 |
| Component: | Core | Version: | 3.2 |
| Keywords: | Cc: |
Description
When there is a CombinedOperator which is frequently applied on the global scope the list of variables in the ScopeView is constantly 'jumping'. This makes selection of a 'jumping' variable while the algorithm is running difficult.
Maybe we could just hide Variables with a GUID name in the ScopeView?
Attachments (1)
Change History (7)
comment:1 Changed 17 years ago by gkronber
Changed 17 years ago by gkronber
comment:2 Changed 16 years ago by swagner
- Milestone changed from 3.0 to 3.2
- Version changed from 3.0 to 3.2
comment:3 Changed 16 years ago by swagner
- Milestone changed from 3.2 to Iteration 0
Milestone 3.2 deleted
comment:4 Changed 14 years ago by swagner
- Resolution set to wontfix
- Status changed from new to closed
In HeuristicLab 3.3 this is not an issue anymore, as the way how a CombinedOperator works has been redesigned completely. Therefore this issue will not be fixed in HeuristicLab 3.2.
comment:5 Changed 14 years ago by swagner
- Milestone changed from Iteration 4 to Current
Milestone Iteration 4 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
Note: See
TracTickets for help on using
tickets.
This is a bit more delicate than I thought. Class Guid doesn't provide a Parse() or TryParse() method and we can't check for type NullData because it's defined in HeuristicLab.Data. A possible workaround is to mark variables which should be hidden with a special tag for instance "##". Also see the attached patch.