Ticket #7512 (assigned)
Expose PeaksViewer Fully
| Reported by: | Owen Arnold | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | major | Milestone: | Backlog |
| Component: | Diffraction | Keywords: | |
| Cc: | Blocked By: | #7013, #8381 | |
| Blocking: | Tester: |
Description (last modified by Owen Arnold) (diff)
We didn't have enough time in iteration 2.6 to do anything other than a quick implementation. The full and proper implementation would be to expose the PeaksViewer via the SliceViewerWindow as an object in it's own right.
A complication here is that the SliceViewer (not the PeaksViewer widget itself), creates the necessary presenters (MVP) to control the GUI. This would suggest that using forwarding methods from the PeaksViewer widget (exposed via SIPs) to the PeaksPresenters would be the correct thing to do.
Once we can instantiate a PeaksViewer object in python, select methods should be provided for exposure on that type directly.
3 Days
Change History
comment:2 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Moved out to backlog as not enough time in R3.0
comment:7 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.1 to Backlog
Moved to backlog at the end of Release 3.1
comment:8 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 8357
I think this can probably be done in 2-3 days