⚠

NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1174 (new defect)

Opened 2012-05-14T14:16:09-05:00

Last modified 2012-08-14T10:34:13-05:00

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 2012-05-14T14:17:43-05:00 by bdezonia

  • Blocked By 1143 added

comment:2 Changed 2012-05-14T14:18:11-05:00 by bdezonia

  • Blocking 1143 added
  • Blocked By 1143 removed

comment:3 Changed 2012-05-30T13:30:02-05:00 by bdezonia

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

comment:4 Changed 2012-06-26T11:00:20-05:00 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 2012-07-03T13:26:11-05:00 by bdezonia

  • Blocking 285 added

comment:6 Changed 2012-07-03T13:28:24-05:00 by bdezonia

  • Blocking 1143 removed

comment:7 Changed 2012-07-03T15:37:44-05:00 by bdezonia

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

comment:8 Changed 2012-08-14T10:34:13-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.