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 #605 (closed defect: duplicate)

Opened 2011-06-14T14:15:19-05:00

Last modified 2011-09-28T15:23:06-05:00

Display sizes do not update after deleting data along the X or Y axis

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej-2.0-alpha5
Component: Display API Version:
Severity: serious Keywords:
Cc: Blocked By:

Description (last modified by bdezonia)

Using the Delete Data plugin you can remove planes. When you do so along the X or Y axis the window display does not resize.

Change History

comment:1 Changed 2011-06-14T14:15:32-05:00 by bdezonia

  • Description modified

comment:2 Changed 2011-06-21T13:16:19-05:00 by bdezonia

  • Description modified

comment:3 Changed 2011-07-28T12:38:37-05:00 by bdezonia

Also true if adding data along X & Y.

comment:4 Changed 2011-07-29T13:27:46-05:00 by bdezonia

  • Milestone changed from biweekly-2011: Jul-18 to Jul-29 to imagej-2.0-alpha5

comment:5 Changed 2011-07-29T13:33:24-05:00 by bdezonia

Related to #627?

comment:6 Changed 2011-08-18T13:17:20-05:00 by bdezonia

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

Also fixed by 64c877fbd4981345c0994d2c3e6016acf8fbfb7a

comment:7 Changed 2011-09-26T14:20:12-05:00 by bdezonia

  • Status changed from closed to reopened
  • Resolution fixed deleted

Do not consider this bug fixed until we have a solution for all three of #605, #627, and #797.

comment:8 Changed 2011-09-26T16:10:04-05:00 by bdezonia

Can still duplicate this bug in alpha 5 and also latest version. There must be a race condition that was never realy fixed. Or switching from ThreadSafeEventService to SwingEventService has somehow caused problems. Investigate.

comment:9 Changed 2011-09-28T15:23:06-05:00 by bdezonia

  • Status changed from reopened to closed
  • Resolution set to duplicate

This bug seems to stem from the same cause as #627. I am closing this ticket as a duplicate but have noted in #627 that any fix needs to test this issue also.