Support and General Use > User Interface and Voice
Pressing LEFT to get to WPS from file root
goffa:
I guess its not REQUIRED to have left to wps, however, it does seem more natural.
Also, the code size only increases by literally 2 lines. (If you take out the comments, and don't make it toggleable)
In the grand scheme, we aren't going to gain much by leaving it out. Some users will gain a lot by having it in though.
I doubt any deciding body will be convinced by my argument, so i'll just stand in my position that it should be included and leave it at that.
Also, given the statistics that 71% of people polled wouldn't mind or would enjoy it. And 10% Don't really care. My math says that the vote is strikingly in favor of having it included. 80/20
AlexP:
The argument that has been used before and is to my mind persuasive is blind users.
It is much easier if you can't see the screen to press left a few times knowing you will end up in root, and can then navigate through the menu structure you can remember. With left to WPS, one more click means you have to restart the whole procedure.
I would much rather have people move their thumb slightly (a minor inconvenience), than mess up navigation for blind users (a huge inconvenience).
Llorean:
Yes, if it is included it HAS to be an option, and it HAS to be off by default. This is, in my mind, not negotiable due to our blind users.
So when being considered you must consider the addition of it as an option.
As well, when you're already too large, even two lines of code can seem like too much if it's a feature only in the sense that it permits people to be slightly more lazy.
Mikerman:
Laziness is human nature and, in fact, is something that should be taken into acccount with player ergonomics, IMHO.
;)
Having said that, if the feature has other impediments that are deemed too costly, such as code size or issues for some users, that of course should affect consideration.
At times I wish that features could be toggled on or off in the compile process. For example, I don't use crossfade, and would much rather have left-to-WPS (I don't know why, but my hands just tend to use it instinctually). But I can forsee many issues with this and don't offer it as a practical solution.
scorche:
You can do that yourself by #ifdefing out all of the parts of the code that pertains to that option. And yes, there are many issues with this. No issues for your own copy of the source, but if it were to be committed like that. Removing features for targets is never a good thing.
That said, there is one feature that you can disable and not compile without any side effects: Tagcache. But that is about it with the CVS source code.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version