Version: 1.3.2 (using KDE KDE 3.4.2) Installed from: Gentoo Packages Compiler: gcc 3.4.4 OS: Linux If I close amarok while listening to a track, then after restarting, I would prefer it to start up paused at that same place within the track.
You mean paused instead of playing? I don't think many people would want that, sorry. We won't add another option for this, for sure.
I dont think I explained it very well. I was basing it on how most of the portable mp3 player work. If I am listening to a mp3, and turn the player off in the middle, next time I turn it on, it starts paused at that same point. It is most effective when listening to audiobooks or podcasts and stuff. I dont think it should be an option, I think that it should be the default behaviour. If there isnt anyone available to work on this and you think its a good feature, then I might be able to give it a crack.
I'm still not sure why you want to it start paused. With amaroK's option "Resume playback on start" enabled, amaroK does exactly what you want, except that it starts in playing state instead of paused. And that won't be changed.
Here is the scenario in which I would use it. - Listening to a podcast, halfway through I decide go to bed, so I turn the computer off. - Next day, I turn the computer back on and wander off to get something to eat, Amarok starts up automatically when KDE is logged in. - I press play and the podcast continues exactly where it stopped the night before. With the "resume playback on start" option, I have to wait for the amarok to start up, then pause it until I'm ready to listen. With the option disabled I have to fast forward through the podcast trying to remember where I left off. I'm not suggesting "resume playback on start" feature changes, however if this is disabled, then starting up paused at the same point as when amarok is closed would solve my problem above.