Paul Louden <[email protected]> writes:
> On 12/21/2010 7:47 PM, Mike Giacomelli wrote:

>> That seems reasonable.  List the parts that are of concern to you and
>> we can commit the rest in the mean time.
>
> The option to turn auto-resume on/off.
> No other options, with the default behaviour when it's on to be "all
> files, but never subsequent files within one playlist."

This sounds reasonable for a first commit, if with the last sentence you
mean "never resume on automatic track change".  The next (or previous)
track should still be resumed when manually started via a track skip
(Right / Left buttons).

Also, I suggest to also consider the 15-second delay for updating the
resume position, with the changes I've outlined in my two last couple of
messages, for committing along with the core feature (or for a
subsequent merge after some more simmering), because it does not need
configuration, is hardly surprising, and adds value of the "do what I
want" kind.

In another message, Mike Giacomelli <[email protected]> writes:

> [...] Once all the lang string issues are figured out, I'll probably
> just split the settings into a separate patch, post it on the tracker,
> and commit the core feature with something like Paul's suggestion.

Just an observation: You do not need to sort out the language-string
deprecation issue ahead of committing the core feature because the
string in question is not needed unless the configuration options are
committed as well.

I'd be happy to help with splitting the patch up by feature.  (I may be
somewhat slow to respond over the holidays, though.)

sideral

Reply via email to