⚠	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 #1329 (reopened defect)

Opened 2012-07-12T12:40:31-05:00

Last modified 2013-03-07T15:49:01-06:00

Display range initialization for float images is crazy

Reported by:	bdezonia	Owned by:	curtis
Priority:	major	Milestone:	imagej2-b8-analysis
Component:	Core	Version:
Severity:	serious	Keywords:
Cc:		Blocked By:
Blocking:	#1244

Description

Make a new 32-bit float image.
Open Adjust Brightness/Contrast.
The min and max values are enormous.

Change History

comment:1 Changed 2012-07-16T14:03:58-05:00 by bdezonia

Blocking 1244 added

comment:2 Changed 2012-08-14T10:51:37-05:00 by curtis

Status changed from new to closed
Resolution set to invalid

I cannot reproduce this bug. Please reopen with more specific instructions if it persists.

comment:3 Changed 2012-08-14T11:07:29-05:00 by bdezonia

The key piece of missing information: during new image creation you cannot specify fill with ramp but instead one of the other options.

comment:4 Changed 2012-08-14T11:07:35-05:00 by bdezonia

Status changed from closed to reopened
Resolution invalid deleted

comment:5 Changed 2012-09-10T15:41:09-05:00 by curtis

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

comment:6 Changed 2013-03-07T15:49:01-06:00 by bdezonia

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