Ticket #4235 (assigned)
More Flexible PeakWorkspaces
| Reported by: | Owen Arnold | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | major | Milestone: | Backlog |
| Component: | Framework | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: |
Description
Need to be able to add additional columns onto a peak workspace to hold information such as
- Number of pixels contributing to the peak
- Peak integrated value
These items (and others) will need to be stored on the PeakObject. Nick suggests putting a property manager on the peak object.
Will also need to ensure that all peaks have the the same information set. Do not want differences in the schemas for different peaks in the same PeaksWorkspace!
Loading and Saving should be handled in a separate ticket.
Change History
comment:2 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:3 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:8 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
comment:9 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5082
Note: See
TracTickets for help on using
tickets.
Moved to iteration 33 at iteration 32 code freeze