Album/Artist/Song listings have no alphabet short cuts.

[GoogleCodeExporter]

This, combined with the fact that names aren't loaded until scrolling stops, 
makes it much more difficult to browse.
Nice to have, if it's lightweight and easy to implement.
Thanks.

Original issue reported on code.google.com by drdocm...@gmail.com on 15 Feb 2014 at 11:56

[GoogleCodeExporter]

On second thoughts, I like the fast scroll bar as it is. Much faster than the 
alphabetised search on the native logitech app.
It would be nice to see alphabet position highlighted as you scroll though.

Original comment by drdocm...@gmail.com on 15 Mar 2014 at 8:42

[GoogleCodeExporter]

Names aren't loaded until scrolling stops to avoid overloading the server, and 
to show you the information 

Suppose you scroll down the song list by flinging, and go past 200 songs.  If 
we fetched all of those, in order, you'd have to wait until the server finished 
sending the details for all of them before it could show the songs at the point 
in the list where you stopped -- unfortunately there's no way to tell the 
server "I know I told you to send me details for songs 120-140, but I don't 
need them any more, I'm cancelling that request."

Also, although the server is supposed to support sending it a request like "How 
many songs start with "A", how many with "B", ..." my experience so far is that 
this is buggy on the server, and can't be relied on.

Unfortunately, Squeezeservers were designed more for access via web pages, 
where you would go through things a page at a time

[ For anyone looking at this after me and wondering how to implement, is's the 
"Z" tag to queries like "albums". On my server I get serialised Perl refs 
returned (of the form "ARRAY(0x...)") rather than the actual array data.

Original comment by n...@ngo.org.uk on 15 Mar 2014 at 1:40

[GoogleCodeExporter]

You're right, and actually the current implementation is quite fast (on a top 
end phone at least, I don't have anything less powerful to test against).
I suppose the logitech app has to load all the details up front then?
It becomes a bit more clunky on the album/songs listing - just because of the 
sheer number of them. It's there that the alphabetical overlay hints would be 
helpful as you scroll. In fact I tried the song listing just now and it's 
taking quite some time to load each page of songs (10 seconds or so), so that's 
not really a good way of finding something. Yes, I'd choose to use the search 
dialogue instead!
Do you have any ideas why the squeeze server isn't reliable in returning the 
alphabetical counts?

Original comment by drdocm...@gmail.com on 17 Mar 2014 at 10:09