Ticket #1308 (closed defect: moved)
Opened 2012-07-10T10:13:27-05:00
Last modified 2012-12-11T15:35:15-06:00
Support IJ1's overlays
Reported by: | bdezonia | Owned by: | bdezonia |
---|---|---|---|
Priority: | major | Milestone: | imagej2-b9-rois |
Component: | Legacy Compatibility | Version: | |
Severity: | serious | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #285, #1399 |
Description
Currently IJ2 translates IJ1 ROIs to IJ2 Overlays and vice versa. We are doing nothing to handle IJ1 Overlays. We should have a flag associated with each IJ1 Roi saying whether it is a ROI or an Overlay. Then translations can respect this distinction.
Note that right now overlays are repeatedly recreated in the harmonizer. We need to track individual IJ1 Roi/Overlay to IJ2 Overlay mappings.
Change History
comment:3 Changed 2012-08-14T12:09:50-05:00 by bdezonia
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta6
Moving to beta 6 (roi conentration)
comment:6 Changed 2012-08-14T13:29:03-05:00 by bdezonia
- Milestone changed from imagej-2.0.0-beta6 to imagej-2.0.0-beta4
Temporary movement. This will go to beta 6 soon after tickets reorganized.
comment:8 Changed 2012-08-29T15:51:14-05:00 by bdezonia
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta6
comment:11 Changed 2012-12-11T15:35:15-06:00 by bdezonia
Note that for beta 6 the current IJ2 Overlay goes across legacy layer as the ImagePlus' Roi and the other IJ2 Overlays go as a set of Rois in the Overlay of the ImagePlus.
comment:10 Changed 2014-05-18T17:37:50-05:00 by curtis
- Status changed from new to closed
- Resolution set to moved
Migrated to https://github.com/imagej/imagej-legacy/issues/8