The touch panel and touch keyboard were an interesting challenge. I picked this one up mainly because the price was well into the "impulse buy" range. I didn't really have a plan for it, but figured it would be interesting to play with. After a little bit of Google-fu, I found that the 4-wire resistive touch panels were rather common, and best of all, there is an Arduino library for it. I also picked up the display because HSC claimed to have data on it. It turned out that used the relatively common T6963C interface. There is an Arduino library for that as well.
I knew I was going to use this display, but wasn't sure how to employ the touch screen. The main quandary I had was that the touch panel was twice the height of the display. The width was about right, but there would be half of the touch panel off the display. What if I dedicated that half of the touch panel to a full keyboard? The top half of the touch panel would interact with the on-screen objects while the bottom half is the keyboard. Here's how it looks:
The items on screen in this photo are part of the "test menu". Those are a bunch of tests that were used for the development. I left them in as part of the device in case I needed to troubleshoot something later.
The touch keyboard class looks like this:
If you look at the whole source code, you can clearly see there was some level of influence by, ahem, Windows... The keyboard employs scan-codes, which represent the "physical" (ok, virtual) keys, which are then translated to Virtual Key codes. Those keycodes coupled with the meta-key state (Shift, Control, Alt) are used to get an actual character (in ASCII) code.
The MetakeyStateChange is a simple "interface" which is implemented by the client code in order to be notified of the internal state of the meta-keys. I used this callback to display the meta-key state on the screen.
If you notice, the constructors only take a reference to the TouchScreen class and no location of the keyboard. This is handled through the Initialize() method into which the CalibrationData is passed in or, it the data is uninitialized, it will invoke a "keyboard calibration" process. That is the purpose of the CalibrationPrompt callback interface. It will ask the user to touch the top-left and bottom-right of the location of the keyboard. This will form the bounds where the keyboard will respond to touch events and translate them to scan-code and characters. The idea is the the CalibrationData is persisted into the EEPROM on the Arduino so the next boot, the keyboard is already calibrated.
The bounds of the keyboard are internally scaled to normalize the bounds to an internal virtual size. Once a touch is determined to be within the bounds, the internal static meta-data is scanned (see the TouchKeyboard.cpp file) to determine the key pressed. getKeyPressed will return keyboard row and column along with the actual point pressed as returned from the TouchScreen class.
Having a full keyboard was really nice to have because I added an SDCard Shield to the Ardunio so that I could save the data. With the keyboard, I could enter a filename into which the data is written using the SD card libraries. Coupled with the on-screen, touch-sensitive object, it also eliminated the need for any other physical buttons or switches. All control and input is handled through the touch panel.
As you can see, it turned out that most of the software I developed for this device was for things other than it's direct purpose. When I present the Bluetooth connected version, the need for sophisticated interactive software was unnecessary... The UI was an Android application I wrote to communicate via Bluetooth.
Next up I'll look at some of the UI widgets and the EventLoop class that brings things together.