OK, the new button code is in! (20060815)
Also Petur was kind enough to sync AGC with the CVS (20060816)
DLed clean CVS, patched with AGC and compiled.
I'm testing the H300 Joystick/LCD remote with my H140.
I also dug out my regular H100 LCD remote for testing.
I do not own the non-lcd H300 remote (yet) so I can't test using that.
Having finally tried out the H100 remote during WRS (which I had never done before) I must ask a question about the H100 LCD remote button mapping:Why are we NOT using the volume UP/DOWN jogwheel to adjust levels?
Why are we using the bitrate/source buttons (a.k.a. -10/+10) instead?
I'm trying to figure out optimal button mapping across all remotes while retaining the cool "Remote Display OFF" feature. I think using volume UP/DOWN would be much simpler and clearer. For clarity sake I've attached some images of remotes and the H1xx with all the buttons labeled exactly the same.
Using the labeling in the images, maybe this would be better in the WRS
- UP/DOWN = 'select item' (same as on main unit)
- LEFT/RIGHT == 'adjust value' (same as on main unit)
- HOLD DOWN turns off the remote's display
- HOLD UP turns on the remote's display
If it's possible to check the state of the remote LCD (on or off) before changing selection (up/down) the user could even be returned to the exact state they were at before turning on/of the remote LCD!
This also leaves the -10/+10 buttons free for whatever else someone dreams up.
I'm of the opinion this is a better way to go. Of course I could be wrong!
Mmmm, Petur, everyone... Wadayatink?
Discuss... EVERYONE: I have re-labelled the remote buttons to illustrate my idea. The hardware is not physically labelled this way neither are the buttons named this way in the source code.
[attachment deleted by admin, too old]