1. You can choose what key signature to work in, both graphically or based on the number of sharps/flats.
2. Several signatures appear identical, but have different meanings. You can change the meaning.
3. The staves are 'hot'. If you hover over a valid place (based on the signature) then the line will be highlighted, and a click will generate a note.
4. The line that transforms the stave area into the keyboard area (via the guideline) contains markers. The solid markers are the primary ones, root=red , third=green , fifth=blue.
   The other notes in the scale are either marked with a black circle if they are officially in the scale, or grey if the are not in the scale.
5. The guidelines are hot and clickable.
6. The keyboard area is clickable, but unlike the stave area in does not care what key you are in.
7. The time controller is scrollable, and also has sub-behavours:
   • You can click and drag an event to a different place.
   • You can hover over an event and then use your mousewheel to shorten or lengthen an event.

MIDI : showMusic loads a primitive routine to connect to MIDI, to send realtime events. Unfortunately I only have Linux systems to test this on, so the only interface module is inc/LinuxMIDI-IO.tcl. The system uses source inc/$tcl_platform(os)MIDI-IO.tcl to load the interface. If the file cannot be found for that OS, it loads inc/unknownMIDI-IO.tcl which provides dummy procs for sendMidiNoteOn and sendMidiNoteOff.
Additional OS dependent code would be very welcome.

The time controller and the play button are exceedingly primitive at the moment. There is no way of choosing the tempo, changing the tempo during the replay, repeating a section etc etc. Any improvements will be warmly welcomed. Please add any other controls etc in a seperate window; I have plans for the remaing real-estate as can be seen by reading the code.

The help engine was cobbled together from tclhttpd3.5.1/bin/mini/mini1.1.tcl and http://wiki.tcl.tk/15244 and http://wiki.tcl.tk/557

The reload button currently reloads the procs for Play , Save and dump.

Save is purely a dummy routine at the moment.

1. Node fog ;
2. EventInSFString S3 ;
3. fog = browser.getNode("Z1") ;
4. S3 = (EventInSFString) fog.getEventIn("set_fogType") ;
5. S3.setValue("EXPONENTIAL") ;

1. Node fog
2. fog getNode {Z1}
3. set S3 [fog getEventIn "set_fogType"]
4. $S3 setValue {EXPONENTIAL}

1. Node fog
2. fog getNode {Z1}
3. [fog getEventIn "set_fogType"] setValue {EXPONENTIAL}

This code benefited greatly from advice freely given by Alex Ferrieux
This code was essential at one stage to make EAI work, but the EAI library has been re-written to work without it. However, OSC is one of the protocols favoured to work with multi-touch interfaces, and this library will therefore be usefull in other situations.

Additional code selftest.kit is a sample that (a) shows how to use the OSC library code and (b) encodes and decodes a collection of arbitary data for testing purposes.

sendtest.kit and recievetest.kit show how to use the library with UDP. You will also need a config file

Install the kits (osclib, selftest, sendtest, recievetest and Tcllib from sourceforge or equi4) and the config file all in the same directory.

You will need a 'batteries included' kit (containing UDP) from somewhere like kbskit.sourceforge.net.