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

Opened 2011-07-22T14:38:26-05:00

Last modified 2011-07-29T11:27:59-05:00

Initialize IJ1 settings after IJ2 settings loaded

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: biweekly-2011: Jul-18 to Jul-29
Component: Core Version:
Severity: serious Keywords:
Cc: Blocked By:


There is incorrect placeholder code in for setting IJ1's options the first time (after IJ2 settings loaded from disk). Determine where in the manager initialization this should happen.

Change History

comment:1 Changed 2011-07-22T14:41:20-05:00 by bdezonia

Idea: throw an OptionsLoadedEvent when IJ2 finishes loading settings. Have Legacy layer react to this event by sybcing IJ1 options with IJ2's values.

comment:2 Changed 2011-07-29T11:27:59-05:00 by bdezonia

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

Forewent event approach. Now just calling optionsSynchronizer.update() in the LegacyService::initialize() method after ij.ImageJ is initialized.