Ticket #1174 (new defect)

Opened 8 years ago

Last modified 7 years ago

Make Overlay Manager a singleton

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b9-rois
Component: Core Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #285

Description

It seems that we should only have one Overlay Manager per ImageJ context. Add code to core that has one UI agnostic overlay manager object per context. And make sure that UI implementations can only ever hatch one window that represents it.

Change History

comment:1 Changed 8 years ago by bdezonia

  • Blocked By 1143 added

comment:2 Changed 8 years ago by bdezonia

  • Blocking 1143 added
  • Blocked By 1143 removed

comment:3 Changed 8 years ago by bdezonia

With commit c737a8803af35e134818b7f1645a2976e179c9d9 there is now one OverlayInfoList per ImageJ context (actually 1 per OverlayService).

comment:4 Changed 7 years ago by bdezonia

Perhaps the OverlayService could own the manager (initialized at startup, destroyed at shutdown, displayed when selected in menubar, and hidden when user closes window).

comment:5 Changed 7 years ago by bdezonia

  • Blocking 285 added

comment:6 Changed 7 years ago by bdezonia

  • Blocking 1143 removed

comment:7 Changed 7 years ago by bdezonia

  • Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4

comment:8 Changed 7 years ago by curtis

  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta6

ROIs will be the focus of beta6.

Note: See TracTickets for help on using tickets.