Support and General Use > User Interface and Voice
Suggestion for unified button mapping for all iriver remotes.
Davide-NYC:
OK, the new button code is in! (20060815) :D
Also Petur was kind enough to sync AGC with the CVS (20060816) :D
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 displayIf 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]
Davide-NYC:
Yo. The remote buttons are BORKED even for regular playback.
What I mean by BORKED is that there is no way (AFAIK) to browse UP using the remote while perusing the file system in file browser mode.
Urghh. Can't get out of a directory!
I think the butons should just map as they are on the main unit.
If there is anything I can do to assist let me know.
Massa:
Please add a bug report to the "BUTTON CHANGES - REPORT PROBLEMS HERE" thread.
It's more likely that Jonathan recognizes your problems if you do so ;)
Febs:
--- Quote from: Davide-NYC on August 16, 2006, 02:19:18 AM ---Yo. The remote buttons are BORKED even for regular playback.
What I mean by BORKED is that there is no way (AFAIK) to browse UP using the remote while perusing the file system in file browser mode.
Urghh. Can't get out of a directory!
--- End quote ---
This was a bug that LinusN introduced yesterday and fixed shortly thereafter. Before filing a bug report, try the most recent CVS build to see if the problem still exists.
Davide-NYC:
--- Quote ---
--- Quote ---Yo. The remote buttons are BORKED even for regular playback.
What I mean by BORKED is that there is no way (AFAIK) to browse UP using the remote while perusing the file system in file browser mode.
Urghh. Can't get out of a directory!
--- End quote ---
This was a bug that LinusN introduced yesterday and fixed shortly thereafter. Before filing a bug report, try the most recent CVS build to see if the problem still exists.
--- End quote ---
I just DLed the lates clean from CVS, and I still cannot browse UP a level using the h100 remote. I think this was not specifically caused by the new button code an may have predated the change. I just rediscovered my H100 remote just for the sake of testing so this may be an old problem.
--- Quote ---Please add a bug report to the "BUTTON CHANGES - REPORT PROBLEMS HERE" thread.
--- End quote ---
I think it belongs here because of the iRiver nature on the problem (multiple remotes) and the fact that some of these button mapping were like this before the major button code changes. I might be tackling a design change rather than a bug per se.
So after a night's rest I understand an inherent problem with remotes in general. Especially the non-LCD H300 remote. (this is probably obvious to everyone that uses it)
If the main unit is in the file browser or the menu you still want your 'blind' remote to function as if it were in the WPS.
* UP/DOWN == volume adjust
* PLAY == play/pause
* LEFT/RIGHT == skip (or nudge) track forward/backwards
Right?
Also I thought of what to use the -10/+10 (source/bitrate) buttons for on the LCD remotes.
-10/+10 could be volume controls while in either 'file browser' or 'menu' modes. So no matter what 'view' you are in at the time you always could turn the volume up/down from the remote. Why not just use the jogwheel labeled VOL you ask? because there is no dedicated volume control on the main unit and it breaks the 1to1 mapping. Whenever UP/DOWN is NOT used for volume on the main unit you reach for the -10/+10 on the remote for volume control WITHOU having to switch views or even look at the main unit. (if it's inaccessible or something)
I am not really that impressed by the jump forward/backward 10 items in a list feature currently. It doesn't take that long to HOLD LEFT/RIGHT and move forward ten items.
Question:
I am willing to generate a master table for all of these remotes and the actions associated with the various screens.
Is there someplace I can look (maybe the wiki) that has all of the available screens?
It would make the task much more manageable. Also, once all of the planning is done it should be an easy coding job (right?) for someone that has the knowledge.
Thanks!
Navigation
[0] Message Index
[#] Next page
Go to full version