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 #1947 (closed enhancement: moved)

Opened 2013-07-12T11:31:44-05:00

Last modified 2014-05-09T11:05:20-05:00

Should RGB images set the legacy "RGB color" flag?

Reported by: curtis Owned by: curtis
Priority: minor Milestone: imagej2-b8-analysis
Component: I/O Version: 2.0.0-beta-7
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1914


When opening an RGB image such as a 24-bit PNG via the File > Open method, ImageJ2 does not report the data type as "RGB Color". In IJ2, there is no difference between this and 3-channel unsigned 8-bit integer, but for IJ1 legacy plugins it matters.

Should we set the RGB flag in such cases?

Change History

comment:1 Changed 2013-07-22T16:22:40-05:00 by bdezonia

  • Blocking 1914 added

comment:2 Changed 2014-05-09T11:03:28-05:00 by curtis

comment:3 Changed 2014-05-09T11:03:34-05:00 by curtis

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

comment:4 Changed 2014-05-09T11:05:20-05:00 by curtis

Hopefully it will be sufficient to support saving 3-channel unsigned 8-bit integer datasets as RGB (maybe as an option). As for legacy plugins, the File > Open command using SCIFIO will probably always open as a composite image; users can manually change it back to RGB Color mode if they need that. This might break old macros though, so we should consider things carefully.

Last edited 2014-05-09T11:05:40-05:00 by curtis