Context Menu on Sansa e200 series

[leptonhead]

Is there anyway to adjust the delay on the keys which bring up the context menus to make them longer?  My Mom is getting thoroughly confused when pressing 'select' on a menu item for a fraction of a second too long does something different than normal.  LOL

[XavierGr]

No, currently there isn't such an option for that, and I don't think there ever will.
Don't you think that it is quite an overkill to add an option for something so trivial?

I think that the best solution for your mother is to get used with the button timings.
In my opinion there is a great time interval that differentiates long and short press.

[leptonhead]

I don't think it's much more trivial than other 'critical' rockbox settings such as beep volume, adjustable wheel light timeouts, clip level hold time, scroll start delay in milliseconds, peak meter release delay, etc.

Whatever the time interval is to bring up the context menu, it's definitely less than a second.  Probably under 500 ms from what I can tell.  A second or more would be nice.

[Llorean]

All of the settings you've listed reflect on things that a human can't change without a setting. Whether or not you press the button quickly enough is something you can quite easily change by simply releasing it slightly more quickly.

It's a question of the fact that there are many, many, many, many settings already. We already think there are too many. In this case, a "sane" value was picked. If you don't hold the button down, you don't get a context menu. It's not perfect for everyone, but we really can't put "every possible setting every human being on Earth could want", and much like keymaps, these are cases where a human can compensate for the lack of setting very easily, whereas a human can't make their ears hear the beeps more quietly relative to the audio, etc.

[cool_walking_]

Would it be possible to have some sort of advanced configuration functionality that lets you configure pretty much everything, like firefox's about:config? It would not be accessible normally, you'd have to go out of your way to get to it. It could just be a text file that you edit.

EDIT: not a feature request, just "do you think this would be a good idea, and why not?"

I guess too many settings could cause code bloat, and unnecessary processing to check the settings.

[Llorean]

It's also an issue of complexity of the source for people to work on it. We don't like hiding settings from the users, in general, but we also want to keep the code trim if and when we can.

[XavierGr]

cool_walking_, if you are so fond of changing the time interval between short and long press, I suggest that it might be easier for you to change it yourself in the source code.

Of course, that might need a couple of hours from your time, to get to know what to change and how to compile, but I assure you that your time will be well spent and that you will be able to change those little details.

[zajacattack]

Or, if you feel up to it. you could create your own build with these custom options. I'm sure a decent amount of people will go for it.

[cool_walking_]

I personally don't have the need for this particular option (or any other that doesn't already exist, really), but I've seen a couple of these requests for strange options that most people would never use, and immediately thought of Firefox's about:config.

As for coding it myself... probably never going to happen since I really, really, really can't code.

[soap]

I personally don't have the need for this particular option (or any other that doesn't already exist, really), but I've seen a couple of these requests for strange options that most people would never use, and immediately thought of Firefox's about:config.

As for coding it myself... probably never going to happen since I really, really, really can't code.

The documentation in the wiki will get you:
A - a build environment
B - source code checked out.
C - a stock compile
D - the ability to add and make patches.

No programming experience needed.
All you then need (after doing A through D on your own) is to come into IRC, and ask someone to point out where this button-press timing is coded in, and to explain how the one line works.
I can't promise anything, but I think if you do A through D you will have no trouble finding someone to help you with this step E.
No programming experience needed.

you then:
F - build your custom build
G - check out source code again in the future
H - step F again
rinse, wash, repeat.