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

Opened 2011-11-10T12:53:36-06:00

Last modified 2014-08-19T11:08:12-05:00

Make IJ2 options/settings applicable to IJ1

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b8-analysis
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1459

Description

We have rewritten all of the IJ1 options dialogs as IJ2 options plugins. And we do synchronization from IJ2 to IJ1.

However some of the IJ1 options are not settable. Rather the IJ1 dialogs run some private code. We need to find these cases and use IJ2 ClassUtils to set private fields (static or not) as possible. As it is now some IJ2 settings have no effect on IJ1 behavior.

Change History

comment:1 Changed 2011-11-10T12:55:12-06:00 by bdezonia

Re: ClassUtils use getField(string) and getValue(field)/setValue(field, val) to set private or package access fields.

comment:2 Changed 2011-11-17T15:49:33-06:00 by bdezonia

Fixed first such case: Overlay Options

comment:3 Changed 2011-11-21T15:58:12-06:00 by bdezonia

  • Milestone changed from imagej-2.0-beta1 to imagej-2.0-beta3

This is taken care of more fully as of 3f41606de95e0c14dd327ee3848b7255d81cdffb. There are some niggling details left as TODOs that we have to handle at some point when more infrastructure is in place.

comment:4 Changed 2012-07-17T16:06:26-05:00 by bdezonia

  • Blocking 1331 added

comment:5 Changed 2012-09-07T11:16:32-05:00 by bdezonia

  • Blocking 1459 added; 1331 removed
  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5

comment:6 Changed 2013-01-22T16:43:18-06:00 by bdezonia

  • Milestone changed from imagej2-b7-ndim-data to imagej2-b8-analysis

comment:7 Changed 2014-08-19T11:08:12-05:00 by curtis

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

Remaining issues have been marked as TODOs for years. And synchronization of ImageJ1 and ImageJ2 data structures is on hold anyway until the ImageJ2 data structures can benefit from another design iteration. See  https://github.com/imagej/imagej-common/labels/data-model for a (non-comprehensive) list.