Bug 5871 - Numeric key selection not correct within Browse New Music
: Numeric key selection not correct within Browse New Music
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-20 06:22 UTC by Philip Meyer
Modified: 2007-10-23 18:30 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
force isSorted off for age level (574 bytes, patch)
2007-10-21 19:44 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2007-10-20 06:22:00 UTC
When browsing New Music, the number keys jump to the first occurence of a track title starting with the letter represented by the keypress.

This is not the correct selection mechanism for New Music, as the song titles are not ordered.

The numeric keypad should allow a position number to be entered, so pressing 5 and 5 should go to the 55th track, not the first track beginning with "K".
Comment 1 KDF 2007-10-20 12:34:43 UTC
we've never had multiple number entry (the enhancement is already filed somewhere).  Numeric entry on unsorted lists is by percentage.  5 goes to middle, 7 goes to 70% etc.  Only the old shoutcast plugin (pre-opml) used to use multiple number entry
Comment 2 Philip Meyer 2007-10-20 12:53:42 UTC
The artist search list uses number entry.  Eg. when I search for "The", I get 38 matches.  If I type 28, it takes me to the 28th entry.

That's how I would expect the New Music menu screen to work.
Comment 3 KDF 2007-10-21 17:32:20 UTC
sorry, my mistake.  number entry is available for long lists.  I expect, however, that new music is appearing as a sorted list, so therefore not taking number entry. The isSorted param needs to be specific to alpha sorting.
Comment 4 KDF 2007-10-21 19:44:46 UTC
Created attachment 2298 [details]
force isSorted off for age level
Comment 5 KDF 2007-10-23 18:30:38 UTC
fixed at change 14051, please reopen if there are any issues.