[Dave McCrea]

I can consider it, although the nature of these changes is tedious, as I start having to add more and more settings to give users fine control over the behavior of the alphabet list. The logic for determining where to jump to when a letter is pressed would also be negatively impacted by this change, as I have an exception for when "#" is tapped, but if I start placing numbers in the alphabet list, then I have to have a lot more logic to figure out where to jump to when a number if pressed versus a letter. There is also the issue of the width of the alphabet bar. If I start inserting 100, 200, etc, that's three characters instead of just a single character, so the bar would have to dynamically expand it's width, but the layout is statically defined (as you get better layout performance from a fixed width), so I would have to make changes across quite a few UIs that have the alphabet bar on them. I'm just trying to call out a few of the many changes that would have to change to incorporate this.

On a side note, you can long press the # icon, then tap 4, then tap 0, then tap 0 if you want to jump to a song starting with 400. You can also change the behavior under Settings->Library Settings->Show Extended Letter List with Tap if you want a single tap to bring up the letter list.

Mike

I understand the complications. I didn't know about the long press # and then a number. That is useful and it helps! 
We have a few charts in the 1000s. To ensure a proper numerical sort, my charts are numbered with four digits with a leading zero for charts < 1000. (eg 0245). 
When I long press #, only a small box appears with 0 and 1 visible (Android). Then pressing the 0 in small box brings up the 0-9 selection.  So if I press 0 then 4, the first chart in the 0400s is at the top of the screen (happens to be 0416 in the book I'm looking at). This works very well and I will use this method all the time. 
Thanks!