From: Mike Holden <rockbox_at_mikeholden.org>
Date: Wed, 31 Mar 2010 15:26:35 +0100

Thomas Martitz wrote:
>> Sorry, but your arguments so far all amount to "this change is
>> better for me, so I don't care if it's worse for you".
>>
>
>
> Except you completely ignore the fact that I proposed the
> confirmation
> screen so that HDD people can live good with it.

Like I said, better for you, worse for me - an added keypress.

>> I feel we need better justification for an increase in code size,
>> complexity and possibly extra settings before this can be
>> considered.
>>
>
> Haha good one, did you copy&paste that sentence from one of various
> other mails or did you actually experiment with it to see how much
> "complexity" and "code size" it adds?

No, it's all my own work! So you're saying the code and binsize are
smaller, and the code less complex with this patch? ;-)

Anyway, we're concentrating on the negatives and the problems,
rather than looking positively towards a possible solution.

How about a new config item "Restart completed playlist on RESUME?"
(or similar, less verbose wording). 3 values: "Never", "Always" and
"Ask". "Never" is the curent situation with a splash and no restart.
"Always" skips the splash and restarts on pressing PLAY (or
autoresume on boot). Ask presents a prompt "Nothing to resume,
restart from beginning?", with Yes and No options. Default value
__must__ be "Never", as that is current functionality. That I think
keeps all parties happy.

Comments (positive if possible!!)?

-- 
Mike Holden
http://www.by-ang.com - the place to shop
for all manner of hand crafted items,
including Jewellery, Greetings Cards and Gifts

Received on 2010-03-31