fix version, license in a separate file
fix version, license in a separate file
Adds LICENSE
Adds LICENSE
Make change event always fire as the user interacts with the knob:
- touch
- wheel
- typing (by binding to the "input" event)

Previously, typing did not update the knob until focus was lost (and
no change event was fired), and
using the keyboard arrows did not fire any change events.

Also move event triggering to val() and change() so it works always
in the same way and less duplication exists.
Workaround for #56 #97
Merge pull request #140 from amuino/consistent_change_events

Always fire a change event when the user interacts with the knob @amuino
Revert fix regression since #140
Make change event always fire as the user interacts with the knob

That is, when using:
- touch
- wheel
- typing (by binding to the "input" event)

Previously, typing did not update the knob until focus was lost (and
no change event was fired), and
using the keyboard arrows did not fire any change events.

Also move event triggering to val() and change() so it works always
in the same way and less duplication exists.

Similar to #130 but fixes an issue with `diplayPrevious`
Merge pull request #143 from amuino/consistent_change_events

Make change event always fire as the user interacts with the knob @amuino
Disable log change
Allow choice of direction; clockwise/anticlockwise

Fixes #105

Creates the `direction` option that allows a setting of `anticlockwise`
to reverse the direction of progression used by the knob. It fully
supports the clicking/touching and `displayPrevious` functionality.

To facilitate extending this behavior to custom draw functions, arc
calculations have been factored out of `draw` into an `arc` function,
which returns the start and end angles, and a boolean denoting the
direction of the stroke.
Update tron skin to use new arc function
Add an example of the direction option