Ticket #1428 (closed defect: fixed)
Opened 2012-08-21T14:31:55-05:00
Last modified 2013-07-12T17:09:55-05:00
Consider changing Image Type menu behavior
| Reported by: | bdezonia | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | major | Milestone: | imagej2-b8-analysis |
| Component: | Core | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1519 |
Description
As new ImgLib types are created the current way we handle the Image Type menu will become unwieldy. Already there are many pixel types that make the menu look cluttered.
We should break the functionality within the menu into two pieces. One piece will show the current type. And rather than a checkmark by "unsigned 8-bit" we could have two string menu entries (one for "unsigned" and one for "8-bit"). This allows us to handle many bit depth and signed and floating combinations with just a few strings.
Selecting one of these type menu entries could launch a dialog that has similar UI to the New Image dialog when specifying data type.
One reason to follow something like this is because Albert and Steffi have been looking into a user defined bit type Type (i.e. 22-bit). We could support this by extracting bits per pix from the image and placing it in the menu. Same with signed, float, etc.
Change History
comment:1 Changed 2012-08-21T14:32:12-05:00 by bdezonia
- Summary changed from Consider change Image Type menu behavior to Consider changing Image Type menu behavior
comment:2 Changed 2012-12-06T11:54:35-06:00 by bdezonia
- Blocking 1356 added
- Milestone changed from imagej-2.0.0 to imagej-2.0.0-beta7
comment:3 Changed 2013-01-22T15:39:32-06:00 by bdezonia
- Blocking 1630 added; 1356 removed
- Milestone changed from imagej2-b7-ndim-data to imagej2-unscheduled