Ticket #290 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

Util.openProcessor does not properly handle RGB data

Reported by: curtis Owned by: melissa
Priority: major Milestone:
Component: plugins Severity: serious
Keywords: Cc: simon.andrews@…
Blocked By: Blocking:

Description

We currently use ChannelSeparator to ensure that image planes are split to so that rgbChannelCount==1 when using the Util.openProcessor method. This is currently sufficient for the Bio-Formats Importer plugin (though that may change; see ticket #289 for details), but it would be nice for external applications such as  FocalPoint to be able to use Util.openProcessor with RGB image data and receive a working ColorProcessor back. Alternately, we could provide an openImagePlus method that gives back an appropriately configured CompositeImage. At minimum, Util.openProcessor should throw an exception if it encounters an unsupported type of image plane.

Change History

comment:1 Changed 12 years ago by curtis

  • Cc simon.andrews@… added

comment:2 Changed 12 years ago by melissa

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

(In [4204]) Changed Util.openProcessor methods to Util.openProcessors. These methods return an array of ImageProcessors (one per RGB channel), and do not assume that the IFormatReader parameter is a ChannelSeparator. Closes #290.

comment:3 Changed 11 years ago by curtis

  • Milestone bio-formats-m2 deleted

Milestone bio-formats-m2 deleted

Note: See TracTickets for help on using tickets.