Looks great! You have enhanced your stuff a lot.
I need to get back to playing with my displays again and try out your later versions of the library. I have been playing with other projects and would like to get back to this soon. I see that I have not updated my thread up on Lynxmotion for quite awhile: (http://www.lynxmotion.net/viewtopic.php?f=21&t=7422&start=124
When I get a chance to continue my play on this, I need to decide if I should continue to do my own work or try to convert over to your library. Obviously yours is far more advanced.
The main issue that I had before was that the code was that controls like buttons was that when the user presses on the button, the code would hang in the button code until the user releases the button, which for a lot of things is fine. But in my case, I am experimenting with a new version of my DIY remote control that uses an XBee to talk to one of my robots, and there are other devices to get data from, such as Joysticks, or buttons, or Nunchucks.... I use a handshake between the robot and the control, that when the robot sends a request for data, the remote needs to respond as quickly as possible. Also there are times when the robot may want to know when a button is pressed and when it is released. Example maybe a button on the displays is used to say fire the cannon and the user wants the cannon to keep firing until the user releases the button. Likewise I was playing with rudimentary slider controls, that for example one may be used to control the height of the robot. The user often will click on the slider and start to drag it up or down and watch the robot adjust its height and when the robot is at the correct height, the user releases the slider...
So I need to figure out if your library can handle this. Probably can figure this out by looking at a more recent copy of your stuff. But would appreciate any hints.
Thanks again for your great work