| Item | Description | Consensus? | Who? | Status | Notes |
|---|---|---|---|---|---|
| 1 | Under Settings/Startup change "Metadata" to something more meaningful like "Data set" | y | Scott | Done | |
| 2 | Settings/VizFeatures: left align "Show X,Y,Z arrows" to be consistent with other tabs | y | Scott | Done | |
| 3 | Capture of an animation sequence appears only possible if key-framing or time stepping. Restore previous capability | n | closed | Need further discussion | |
| 4 | Consider separating time animation and key-framing. They seem to be different things | n | closed | Needs further discussion | |
| 5 | The Navigation/Animation tab centers many of the widgets (e.g. Frame Step Size). Elsewhere (e.g. Settings/VizFeatures) we left and right justify. Need to be consistent. | y | Scott | Done | |
| 6 | Left justify widgets on Navigation/View | y | Scott | Done | |
| 7 | The fidelity selector doesn't display well on the Mac. Could we replace with an integer (discrete) slider bar? | y | Alan | in-progress | Limit number of fidelity settings to whatever will be displayable on the screen (8?) |
| 8 | Contours/Appearance tab: Add slider bars for "line width" and "Text size". | y | Scott | Done | How do we normalize line width? Currently width is in terms of voxels (at highest refinement). Note that these settings should get an asterisk, and support saving to startup settings. |
| 9 | Contours/Appearance tab: left justify | y | Scott | Done | |
| 10 | Large numeric values (e.g. some data domain coordinates/sizes) often aren't legible. For example, load KatrinaMaster.nc, enable contours, and examine the "user extents" on the Contour/Layout tab. We should have a user preference that specifies a C style formatting string that is used for all numeric values that have the potential to be large. | y | Alan | Done | Specify number of digits. See if that works. May look at C format string or other options.Consider table layout with cells with borders. |
| 11 | Crop any bounding rectangles (e.g. Contour layout) to the domain bounds so that when they're rotated under stretched coordinates the result isn't an unusable region that extents far outside of the domain. | y | Alan | Done | Try simple thing first: crop to twice the domain size. |
| 12 | With VDC3 there is sufficient metadata to determine which variables are vectors (usually). We should exploit this to make better choices for default variables for the barb and flow renderers | ? | post-poned | If possible. Need to explore CF metadata properties. | |
| 13 | Provide a slider bar for Contours/Appearance "barb thickness" | y | Scott | Done | Need asterisk too. |
| 14 | Make TF editors consistent between tabs. Contour uses label "Histo Bounds", while Barbs uses "TF domain bounds". | y | Scott | Done | |
| 14.1 | Barbs has "discrete color map" option, Contour does not. Barb does not. | y | Scott | Done | |
| 15 | The height variable on the Barbs/Variables table is named labeled "height". But on the Barbs/Layout tab it is labeled "terrain". Be consistent. | y | Scott | Done | |
| 16 | The default render name shown in the "Select new renderer" box should be the actual name that will be used, not "Renderer Name" | y | Alan | Done | Not easy to do because name is not available when dialog is presented. Instead provided blank text with tooltip. |
| 17 | Make the default barb thickness larger. The default is very hard to see | y | Scott | Done | |
| 18 | Use a unitless number for the barb length scale factor. E.g. The first time the barb tab is enabled determine the max (or maybe average) vector length. Compute a scaling factor that yields a max (or average) vector that is some fraction of the domain size (e.g. 1%, 5%). Map this to the "Barb Length scale factor" equal 1. I.e. the default scale factor is always 1, and this results in a max (average) vector length of some % of the domain size. | y | Alan | Done | May need to do some experimentation to decide default internal scale factor (what get's displayed to the user should be a 1.0) |
| 19 | Explore preventing subtab selectors from scrolling when scroll bars are present in a tab. | y | Scott | post-pone | Priority may not be so high if tabs with scrollbars are redesigned to not need scroll bars. Not easily doable. |