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 #1215 (closed defect: fixed)

Opened 2012-06-13T13:58:16-05:00

Last modified 2012-06-19T17:02:36-05:00

Overlay Manager flatten command displays all white

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b3-headless
Component: Display API Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1143


Open Organ Of Corti. Open Overlay Manager. Run Flatten command from Overlay Manager. An all white window is displayed. One can see using pixel probe that the pixel values actually vary widely. For some reason the display code is malfunctioning. (Note the flatten command was not entirely finished in that it does not draw the current ROI's outline which is immaterial for this bug).

Change History

comment:1 Changed 2012-06-13T14:55:36-05:00 by bdezonia

  • Blocking 1143 added

comment:2 Changed 2012-06-19T15:03:31-05:00 by bdezonia

Notice that the displayed image is also missing the Channel slider. It should always be present for a merged color dataset.

comment:3 Changed 2012-06-19T15:05:59-05:00 by bdezonia

Dragging window size around does not create slider. But use the ">" or"<" hotkeys (axis position forw/back) and the slider shows up and the data is drawn correctly. Is this another failure to setActiveAxis() initially?

comment:4 Changed 2012-06-19T15:36:51-05:00 by bdezonia

Making DefaultImageDisplay initActiveAxis() at least once does not fix this problem.

Is it possible that the way the display is created avoids the DisplayPostProcessor and that causes problems?

comment:5 Changed 2012-06-19T16:15:09-05:00 by bdezonia

The order of event processing changed recently. This could be a results of that. But I think I discovered the bug before Curtis made the event order changes. Investigate.

comment:6 Changed 2012-06-19T17:02:36-05:00 by bdezonia

  • Status changed from new to closed
  • Resolution set to fixed

Fixed with commit 8960ffe0729108c4840c84bea430845b9a7874f0.

It does not appear that the event order changes created this bug. Those changes happened a couple days after this bug was reported.