calculated in one call.

trace utility for debugging

to be available to non-fslview things. Moved orientation constants
from fsl.data.image to (new module) fsl.data.constants, so circular
imports are not necessary.

There could still be some bugs lurking ..

contain layout definitions for all of the things. A couple of useful
little actions on OrthoViewProfile.

working nicely (aspect ratio/proportional canvas sizes). Does not yet
support labels, but about to add that in.

floating point values, instead of being passed a props.Bounds object.

of in OrthoPanel, so it can be used by render.py

numpy.dot). And a few tweaks elsewhere

between each of the three spaces (voxel, display, and world)

matrix), LightBoxPanel (not passing displayCtx to LightBoxCanvas),
fslview_parseargs (using imageList.bounds instead of displayCtx.bounds),
ImageList (didn't remove bounds-related code), ImageDisplay (attempting
to offset transformation matrices for affine, when only supposed to do
it for id/pixdim)

to use transform module instead of image.voxToWorld/worldToVox methods

coordinate systemss, with the ultimate aim of having the location panel
always reporting image world coordinates, regardless of the way in which
images are being displayed.

location (one-off)

New module, fsl.gui. for generic gui stuff. Rolled my own Notebook widget, as none of the wx ones were any good. Still having auto-layout problems.

Support for displaying items in reverse order. I need to add some wrapper methods for adding/removing items, with reverse support.

Support for multiple images, from a predefined list. Am now going to try and add support for adding/removing images at runtime.

ImageView supports multiple images. Pretty hacky at this stage, needs cleaning up. Have gone back to storing image data as uint8s.

SliceCanvas supports multiple images. Well, it looks like it should, but I haven't yet tested it with more than one.

GL buffer handle is now stored in fslimage.Image object. Removed notion of 'master' canvas from SliceCanvas - a shared GL context may be passed in directly. BUT if a shared context is not used, and the program attempts to share image buffers, it will segfault. Need to think about that one.