Auto-resume on startup ability

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Click DAAP saved server icon
2.Wait for library to be downloaded
3.Must select songs. Does not resume.

What is the expected output? What do you see instead?
I'd like the app to be like a simple radio which you can quickly turn on to 
start hearing music ASAP because it currently takes too long to get this app to 
play. I would like the option to resume play where it left off. There could be 
a checkbox in settings "Resume on start". If checked, DAAP would keep track of 
it's current state including:
-which server
-which library
-which song
-random skip (on/off)
-loop track (on/off)
-time in current track
When DAAP is restarted later, if "Resume on start" is checked, it could for 
this saved information. If it exists then it could:
-log into server (fail if can't connect)
-select library (fail if can't find library)
-select song (fail if can't find track)
-set random skip to previous state
-set loop mode to previous state
-skip to saved time in track
-automatically press PLAY

What version of the product are you using? On what operating system?
.9.5.5 on Android 2.3.4

Please provide any additional information below.
-perhaps this functionality should be built into the "shortcut" building 
interface so that it wouldn't be an app-wide preference. That is, when creating 
a shortcut, in addition to entering the server info there could be the option 
"Resume on start". That being said, I personally wouldn't mine an app-wide 
preference.
-sort of unrelated but it would be great if the library database could be 
cached so app launch could be even quicker

Original issue reported on code.google.com by anthonyo...@gmail.com on 29 Aug 2011 at 3:30

[GoogleCodeExporter]

Forgot to mention, to complete the resume capability it would be great if DAAP 
would also save the Queue (if it exists) and resume it's place in the queue on 
start.

Original comment by anthonyo...@gmail.com on 29 Aug 2011 at 3:33

[GoogleCodeExporter]

I like this idea and it probably wouldn't be too difficult to implement; so, 
hopefully you'll see this is the next version.  But it may be little while 
because I'm busy with work recently.  Thanks for the suggestion!

Original comment by michael.miceli88@gmail.com on 5 Sep 2011 at 2:45

• Changed state: Accepted