Hi,
Firstly and with respect, it might be good to change the title of this thread to make searching better. Change the "8" to a "9" etc
ok. I played a lot with the touch screen and found it less easy to use than I expected. I didn't find a good helper library - apologies if one does exist and please let me know and then ignore the following.
My application needs a number of screens, each with different areas to touch onto, some screens use the same overlapping areas etc. I also found that the data returned by the touch screen can vary wildly according to how hard it is touched, what is touching it, and how well the screen is supported (if bolted down or flapping around on a protoboard - makes a difference).
I can't claim to have solved this 'nicely' or overly well but I have written into my project routines to define areas of the screen then return digits to indicate which area was touched. Also, because there are a few screens, it allows selecting only from one of a key set (ie on the keypad screen, only return hits from the defined keys). I found (running in landscape mode) that about 50 pixel width & height areas work well - smaller than this can be difficult to accurately hit (this may be because of my non-clever code or fat fingers... not sure).
I didn't implement a keypad as such - I used a rotary encoder and have multiple "step" sizes ranging from "1" to "10,000" per step (it is a software controlled radio, not sdr as such).
Let me know if you want the code - I'll chop it out and make a test program. Might take a day or three tho.
Cheers - Richard
I had to address the touch routine by averaging/massaging its output somewhat because of the above.