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 #1290 (closed defect: wontfix)

Opened 2012-07-05T15:59:06-05:00

Last modified 2014-12-18T12:39:49-06:00

First zoom operation has problems

Reported by: curtis Owned by: curtis
Priority: major Milestone: imagej-2.0.0
Component: Display API Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #871, #1439


The first time a zoom operation is performed on the canvas of a new display, the behavior is erroneous.

For example, if you call Set Zoom on Boats with 500% zoom, and centered on (400, 400), the center will be wrong afterward. But if you call it a second time, all is well.

Similarly, if you open a dataset from disk and then zoom in or out, the panel will repack strangely the first time. But if you rezoom, the problem goes away.

Perhaps there is a one-time state flag screwing things up somewhere.

Change History

comment:1 Changed 2012-07-05T16:46:29-05:00 by curtis

  • Blocking 871 removed

(In #871) This bug is a side-effect of a more general bug: the first time a canvas zoom operation happens, it misbehaves. If you rerun the Set Zoom plugin a second time, the canvas is updated correctly. See #1290.

comment:2 Changed 2012-07-12T10:51:26-05:00 by curtis

  • Blocking 1326 added; 1185 removed
  • Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4

comment:3 Changed 2012-07-12T10:51:47-05:00 by curtis

  • Blocking 871 added

comment:4 Changed 2012-08-27T14:43:58-05:00 by curtis

  • Blocking 1439 added

comment:5 Changed 2012-08-27T14:44:14-05:00 by curtis

  • Blocking 1326 removed

comment:6 Changed 2012-08-27T14:45:14-05:00 by curtis

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

comment:7 Changed 2014-12-18T12:39:49-06:00 by curtis

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

Closing as "good enough for now"—especially since the Swing UI is not the default right now anyway. This issue will probably rise again someday, after the Swing UI is in more use. But that UI may undergo substantial changes before that happens...