One of the things I miss with the Twiddler is scrolling. In the tuner there is an entry in the Look Up list called HID code, so out of curiousity I looked up whether there were any promising ones. I jotted down a few, but immediately ran into issues.
It says the way to invoke it is < keystroke > (with a trailing space, but not the leading space. That is there because it's the only way I can get the boards to accept anything starting with <
< keystroke >0x22
< keystroke > 0x22
< keystroke 0x22>
< keystroke 22>
< keystroke > 22
< keystroke >22
< keystroke 34> (the decimal version since 0x22 is apparently hex)
< 0x22 >
In the cases without < keystroke > it just output < 0x22>. In the case of the < keystroke > entries it seemed to act as page down. Same thing with the other five or so keycodes I tried.
Incidentally, the keycodes that seemd promising were:
0x22 Finger (potential swipe activity if it can be combined with the joystick for 'flinging' things up and down
0x33 Touch (same as above)
0x34 Untouch (figured that if touch was the solution then I'd need to untouch stop it from moving the screen around)
0x38 wheel (possibly middle click, possible scrolling, possible just wheel like the unix group wheel
0x40 Vx (either the name or maybe what was above it made me wonder if it might mean movement on the x plane)
0x41 Vy (same, but where x is side to side y would be up and down)
0x42 Vz (just wondered what the heck it was. 3d?)
So how does keycode > work? Is it as simple as just being assigned to a key, and when it's pressed I type in the keycode?
Send any code, in decimal, listed on the Keypad HID code page (0x07) found on USB HID Usage Tables (HUT)
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf (section 10, p. 53)
Unfortunately this kills my hopes at this stage since it is restricted to the keyboard table. Oh well.