Search requires too many button presses

Posted by: tonyc

Search requires too many button presses - 12/11/2001 23:05

Instead of hitting Search six times to search by source or 5 to search by genre, why not have it like this:

Search then "2" search by artist
Search then "3" search by source
etc... i.e. it should use the numbered buttons as they are currently used for the "more from this.." or "hate this.." features. I realize numbers are also used to type in the search criteria, but it's much less of a pain to hit "search" "2" and then type in an artist than it is to hit Search EXACTLY four times. Especially when using the remote in the car and you're not sure the player is going to receive the code. It would require a lot less looking at the display and a lot less button presses.

Since there's no # for "PIN" currently I guess it could use 1. So "search" "1" '1234" or something.

This might have been suggested before but I think it would be a real improvement. My brain is programmed like "artist=2" "year=6" etc. Why not put that to good use...
Posted by: rob

Re: Search requires too many button presses - 13/11/2001 04:51

That was the plan, yes.

Rob
Posted by: tonyc

Re: Search requires too many button presses - 13/11/2001 09:20

Was the plan? Did it slip out of the 2.0 baseline? It seems trivial to implement...
Posted by: tfabris

Re: Search requires too many button presses - 13/11/2001 10:29

It seems trivial to implement...

Except that it directly conflicts with the PIN entry box. So implementing it would require changing that UI.

Personally, I've gotten used to pressing Search three times to reach Artist and it doesn't bug me in the least.
Posted by: tonyc

Re: Search requires too many button presses - 13/11/2001 11:05

You must have missed my discussion of the PIN issue. Searching by PIN could be accomplished by "Search" then "1" to search by PIN.

I realize this is a small change to those who use PIN (they would have to type in one extra button press) but for those who use Artist, Genre, Source searches, it's a huge win. Making sure a remote button press "gets through" six times is difficult even with beeps, and in 2.0b3 there is a more noticable delay between when you hit search and when it switches to the next search view.
Posted by: eternalsun

Re: Search requires too many button presses - 13/11/2001 11:37

This sounds good.

Calvin
Posted by: loren

Re: Search requires too many button presses - 13/11/2001 12:42

I've whined about this before, and that's the perfect solution. It's a much more logical implementation.