In case you've not seen the various threads I thought I'd related what has happened and what's going to happen with AutoTouch.
1) I did finally get around to adding the ability to any button to have a notication of the button being pressed. So that's there now
2) I've changed it so that each form will resize to the size of the background image given to it, giving the ability to effectively make a skin for any size screen
What I'm planning on doing.
1) I'm messing about with the architecture so that anyone can write a new form. The whole thing is .Net based so you'll create a new form by subclassing of my type and then just putting the DLL in the directory with AutoTouch, Then you can reference the DLL in your skin file and it'll load up and work just great. This means that someone could easily add a DLL to navigate with another program for example. You'll also be able to call back into the main autotouch to do things like pause the currently playing audio (as the nav system does when it announces an upcoming turn) and call back to put up a keyboard or a choice screen as I have now, if you don't want to write your own. There are also several callbacks that will be available to you to help parsing skin files.
2) As part of #1 I'm going to pull out the MapPoint Navigation and make it's own DLL That can either be used or not, this will serve two items, one is to make it possible to use other nav systems, and 2) is to make it possible to maybe do an open source release of the core AutoTouch System. The thing preventing that release now is that I'm using a purchased GPS Decoder for the mapping stuff and I can't release the source code that uses that library because it's lisensced to me.
Does this jive with what people are expecting from this project now?