because whynot. Also adjusted String.cast method to be less silly.

BoundsValueList class.

collision with fslpy/notifier

can be customised

passed to __init__. Now supported on choices added after creation (via
addChoice/setChoices methods).

properties now explititly allow string versions of choice values.

'str', instead of six.string_types.

specific value

when creating a widget.

elsewhere.

a choice widget is created

longer accepts labels - these can now only be set via
makeWidget/buildGUI. Something similar will probably happen to Point and
Choice properties. Warning note added about List widgets

files (they'll be re-generated again probably soon)

for getting/setting item constraints, which were never used.

are now local to the function that uses them (e.g. matplotlib,
numpy). GUI related functionality is now loaded by the application code
explicitly calling the props.initGUI function, so that wx is not
implicitly imported.

said default labels are forced to be strings.

conversion made a bit smarter, and case insensitive.

values which will be accepted for assignment.

bounds for all axes.

default values, persisting current selection, etc. A few associated
additions to the EditableListBox interface. A little interactive test
case for choice property widget stuff.

were not being notified on choice update

that a point is within its bounds.

rais a ValueError.

binding. Related changes to Choice._updateChoices method. Some new
utility methods on HasProps class to enable/disable notification of
all properties.

the build_parts ViewItem specifications)