Ticket #693 (closed defect: wontfix)
Opened 2011-07-27T09:54:47-05:00
Last modified 2014-08-19T11:18:22-05:00
ij.gui.Overlay not tracked in legacy layer
Reported by: | leek | Owned by: | curtis |
---|---|---|---|
Priority: | major | Milestone: | imagej2-b9-rois |
Component: | Legacy Compatibility | Version: | |
Severity: | serious | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #285, #1011 |
Description
ImageJ 1 overlays are not tracked in the legacy layer. An overlay appears to be a group of ImageJ 1 ROIs. It's accessible through ij.gui.ImageCanvas which is accessible through ImagePlus.getCanvas.
I suppose we need to determine how to model and support this. Unfortunately, "Overlay" in ImageJ 2 is pretty much synonymous with ROI in ImageJ 1, so the naming is confusing. I (LEEK) can be in charge of implementing an overlay collection that mimics the ImageJ 1 behavior, but I wanted to get guidance on what to do and what the plans were before proceeding. Alternately, the grouping could be represented in the overlay manager and it could be Adam's job to implement.
I'm assigning it initially to Curtis to get direction on what to do.
Change History
comment:1 Changed 2011-10-19T13:54:45-05:00 by curtis
- Milestone changed from imagej-2.0-beta1 to imagej-2.0-beta2
comment:3 Changed 2012-06-08T12:24:58-05:00 by curtis
- Component changed from bio-formats to ij-legacy
comment:5 Changed 2012-07-12T17:27:04-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4
comment:6 Changed 2012-08-14T10:32:11-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta6
ROIs will be the focus of beta6.
comment:7 Changed 2012-12-11T16:04:59-06:00 by bdezonia
This may be complete with some Roi/Overlay sync code put in place for beta 6. Curtis please review (discuss with me if needed) and decide whether to close or not.
comment:9 Changed 2014-08-19T11:18:22-05:00 by curtis
- Status changed from reviewing to closed
- Resolution set to wontfix
Synchronization of ImageJ1 and ImageJ2 data structures is on hold until the ImageJ2 data structures can benefit from another design iteration. See https://github.com/imagej/imagej-common/labels/data-model for a (non-comprehensive) list.
This is a very important feature for full backwards compatibility but will have to wait till the second beta, as there are too many other high-priority tickets. But it is absolutely a "must have" for the 2.0 final release.