Task #4840 (closed)
Opened 13 years ago
Closed 12 years ago
DB/Model: ROI Polygon and Polyline
| Reported by: | jburel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | ajpatterson, jamoore |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jburel)
Good to have but not top priority
Replace Polygon by closed Polyline.
Related to #4317
Solution might be for now to allow save/upgrade data from client
Change History (9)
comment:1 Changed 13 years ago by jmoore
comment:2 Changed 13 years ago by jburel
- Description modified (diff)
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:3 Changed 13 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:4 Changed 13 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:5 Changed 13 years ago by jmoore
Referencing ticket #4891 has changed sprint.
comment:6 Changed 12 years ago by jburel
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Priority changed from minor to major
Since we have to parse the string defining the polyline
instead of having a polyline+closed flag
The model should be: if start point = end point then that's a polygon.
e.g. a, b, c, a for a polygon and a, b, c for polyline.
Change has to happen at the model level instead of DB.
comment:7 Changed 12 years ago by jburel
- Cc jmoore added
- Owner jmoore deleted
- Summary changed from DB: ROI Polygon and Polyline to DB/Model: ROI Polygon and Polyline
comment:8 Changed 12 years ago by jburel
Clarification:
Better to remove the flag from the model, and only differentiate between polyline and polygon using the sequence of points.
comment:9 Changed 12 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
The decision is: re-introduce polygon. The ticket is invalid and can be closed.
Referencing ticket #2568 has changed sprint.