Rockbox mail archiveSubject: Re: jdgordon: r21307 - trunk/apps
Re: jdgordon: r21307 - trunk/apps
From: Paul Louden <paulthenerd_at_gmail.com>
Date: Tue, 16 Jun 2009 17:14:51 -0500
> But as long as they get abortable I don't have any strong opinions on
> that detail.
I think abortable timed splashes is a recipe for accidental keypresses.
If different splashes have different times it makes it very easy to
accidentally trigger something else with the keypress you meant to abort
with (especially if not all splashes are abortable). If all splashes are
the same length, it's still quite possible to be a bit too slow on the
button press, and you've added in the factor that now many splashes are
longer than they used to be, or need to be. If only one key can abort,
this adds in a further factor that many of our users won't know about
the abort key, and basically be stuck with longer splashes all around
without any clue why. New users will just think this is the way the UI
works - long splashes.
It seems to me, at least, either splashes should just timeout without
the option to abort, in a reasonable time frame dependent on the splash,
or they should all be abortable with any key (or at least a couple
obvious keys, maybe select and cancel) and never timeout. I think
"accidental abort of a splash" is less frustrating than other things
that can happen if the splash disappears just as you press the button.
Received on 2009-06-17