Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 9.0.1 Minor Release
-
Labels:None
-
Story Points:3
-
Sprint:Fall 2017
Description
Currently, when a new track is added, a row is inserted in the data management table at some random position.
There is code for ordering the rows, but it is not implemented effectively.
Current task:
Fix the existing method to
a) make slightly more sense,
b) actually work
The position of a new track added to the table should be consistent and predictable.
This ordering is handled by featureTableComparator in DataManagementTableModel.java.
When datasets are initially passed to DataManagementTableModel functions, the datasets are ordered alphabetically. This order may is then lost when we pass it through a hash map in the function feature2StyleReference.
Ideally, the order would reflect the order in which tracks were added, but that is a larger scope and a separate issue (see related issues).
Attachments
Issue Links
- relates to
-
-
- To-Do
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Summary | Make track order in Data Management Table same as main view | Make track order in Data Management Table logical |
| Description |
The order of tracks in the Data Management Table (top to bottom) should update whenever there is a change to the main view, so it always matches the order of tracks (top to bottom) in the main view.
Need to establish how to handle hidden tracks. |
Currently, when a new track is added, a row is inserted in the data management table at some random position. There is code for ordering the rows, but it is not implemented effectively. Current task: Fix the existing method to a) make slightly more sense, b) actually work The position of a new track added to the table should be consistent and predictable. Ideally, the order would reflect the order in which tracks were added, but that is a larger scope and a separate issue. |
| Description |
Currently, when a new track is added, a row is inserted in the data management table at some random position. There is code for ordering the rows, but it is not implemented effectively. Current task: Fix the existing method to a) make slightly more sense, b) actually work The position of a new track added to the table should be consistent and predictable. Ideally, the order would reflect the order in which tracks were added, but that is a larger scope and a separate issue. |
Currently, when a new track is added, a row is inserted in the data management table at some random position.
There is code for ordering the rows, but it is not implemented effectively. Current task: Fix the existing method to a) make slightly more sense, b) actually work The position of a new track added to the table should be consistent and predictable. This ordering is handled by featureTableComparator in DataManagementTableModel.java. When datasets are initially passed to DataManagementTableModel functions, the datasets are ordered alphabetically. This order may is then lost when we pass it through a hash map in the function feature2StyleReference. Ideally, the order would reflect the order in which tracks were added, but that is a larger scope and a separate issue (see related issues). |
| Sprint | Sprint 39 [ 47 ] |
| Rank | Ranked lower |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Open [ 1 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | Screen Shot 2017-04-20 at 12.59.39 PM.png [ 13958 ] |
| Assignee | Ivory Clabaugh [ ieclabau ] | Ann Loraine [ aloraine ] |
| Status | In Progress [ 3 ] | Open [ 1 ] |
| Priority | Major [ 3 ] | Blocker [ 1 ] |
| Status | Open [ 1 ] | Pull Request Submitted [ 10101 ] |
| Story Points | 3 |
| Status | Pull Request Submitted [ 10101 ] | Needs Testing [ 10002 ] |
| Status | Needs Testing [ 10002 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Assignee | Ann Loraine [ aloraine ] | Ivory Clabaugh [ ieclabau ] |
| Assignee | Ivory Clabaugh [ ieclabau ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Ivory Clabaugh [ ieclabau ] |
| Assignee | Ivory Clabaugh [ ieclabau ] | Ann Loraine [ aloraine ] |
| Status | Reviewing Pull Request [ 10303 ] | Needs Testing [ 10002 ] |
| Assignee | Ann Loraine [ aloraine ] | Mason Meyer [ mason ] |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Fix Version/s | 9.0.1 Minor Release [ 10500 ] |
| Workflow | Loraine Lab Workflow [ 17730 ] | Fall 2019 Workflow Update [ 19785 ] |
| Workflow | Fall 2019 Workflow Update [ 19785 ] | Revised Fall 2019 Workflow Update [ 21904 ] |