Rockbox Development > New Ports
Cowon D2
Llorean:
I'm not saying something more complex shouldn't be worked on if there's a real place for it in Rockbox, but at the same time, with 12 additional "buttons" from just the vertical and horizontal gestures on a 3x3 grid, you probably run out of features before you run out of jobs.
As for the touchpad driver being too slow, do you mean you're afraid someone might move the stylus too far, and perhaps go from "Top Right" to "Top Left" without it picking up "Top Center" at all?
cybergrind:
why touchscreen driver should work slow?
JdGordon:
--- Quote from: Llorean on April 14, 2008, 07:13:31 AM ---As for the touchpad driver being too slow, do you mean you're afraid someone might move the stylus too far, and perhaps go from "Top Right" to "Top Left" without it picking up "Top Center" at all?
--- End quote ---
yes, well no... umm... how it works on the mr500 is that touchscreen stores each press as they come in, but the actual button driver doesnt poll very often (realtivly), in combination with cpu speed and threading I'm not sure how reliable it will be.. but remember, this is all without doing any testing on either target so I could be wrong.
JdGordon:
woo :D it works...
the touchscreens now have 21 "buttons" :p
so now lets drop this subject and just deicde if we want this code in or not... we can discuss how to use the buttons in another thread
shotofadds:
I haven't had time to have a proper read of the code, but if it works I say get it in and tweak later, if necessary.
I spent yesterday attempting to get some sound out of the D2 (unsuccessfully), but I might hold off that for a while and get the touchpad working first.
If the button driver is going to be polling the touchscreen, I needn't worry about having the pen-down event driven from an interrupt. Which is handy, as it doesn't seem to be too reliable. :-\
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version