Rockbox Development > New Ports
Cowon D2
Llorean:
Or you could just link him to the information in our wiki. The information he could've found if he'd searched like required to by the guidelines. http://www.rockbox.org/twiki/bin/view/Main/CowonD2Info
Shady:
oops! Sorry andiator, guess I've mixed up the controls. They are flipped now, i mean the up is down and the left is right ;D Anyway it is better now than before ;)
andiator:
Ok, updated rockbox.zip again.
JdGordon:
shotofadds: I dont think I have your email so ill comment on the touchpad test plugin here...
its more of a general issue than anything for the actual plugin..
1) use SOURCES for hhte #ifdef HAVE_TOUCHPAD instead of wrapping the whole .c file in them
2) always add functions to the end of the plugin api or you break builds unless a full rebuild is done.
3) "intptr_t button_data; /* why intptr? */" because void* and int are different sizes on 64bit sim builds, so this stops the warnings
4) there is no way to switch between stylus and button mode?
other than that, it looks good...
http://www.pastebin.ca/1003385 for those having no idea what im talking about
shotofadds:
As it's a test_* plugin it'll rely on people manually adding it to SOURCES, so I'll remove those HAVE_TOUCHPAD ifdefs - they're rather pointless.
I don't really understand "add functions to the end of the plugin api or you break builds unless a full rebuild is done". Surely the very act of updating plugin.h causes all plugins to be rebuilt? (but that's rather off-topic for this thread I guess...)
As for the intptr_t, I wasn't sure why button_get_data returns a pointer type at all - surely it's just a 32 bit int (int32_t or somesuch?)
I'll add a switch for the stylus mode (can you suggest a button mapping for the m:robe?) and then we're in business.
This plugin has already shown up a couple of issues on the D2:
1) Touching on/near the 'line' between two areas causes jitter between the two adjacent rectangles. This causes a stream of distinct button presses.
2) Small, slow movements are shown with a fast update rate, but faster movements are shown with a really slow update rate (is this the HZ/5 thing?)
3) A continuous movement of the stylus seems to work fine, but when used for individual button presses I occasionally get a 'random' extra button event, before the actual press.
Do you see any of those things with the m:robe?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version