0.9.4

Consistent change events

Change events ( change:[property]) are now fired on programmatic changes as well as changes caused by user interaction. Also, they are now fired for all properties, even if the property is not explicitly supported by the widget. The listeners now have three parameters: widget, newValue, options. options is an object that may be given to the set method as the last parameter. All change events triggered by that set will then receive this object. If no options object was given, it will be empty in the change event.

New/renamed event types

• All events of the type selection are now select.
• The SearchAction event submit is now accept, and modify is now input.
• All widgets with a selection or selectionIndex property now have a select event. It behaves like change:selection, but is only fired when the selection property changes due to user interaction.
• The TextInput widget now has an input event. It behaves like change:text, but is only fired when the text property changes due to the user typing.
• The Picker previously fired change:selection, which should have been change:selectionIndex. This has been corrected.

Listener parameters changed

• Like with change listeners, all other listener now also get the widget that fired the event as the first parameter. All existing parameters are shifted by one.