Rockbox mail archive
Subject: Re: Autoloadconfig thingy - wanted: feedback :-)
Re: Autoloadconfig thingy - wanted: feedback :-)
have you tought about a OnAcPower.cfg ?
This would save you from modifying the existing user interface.
And it would perfectly meet your needs, as I suppose you're having the
charger next to the stereo, like I have.
On Thu, 31 Mar 2005 19:29:00 +0200, Ronald Teune <firstname.lastname@example.org> wrote:
> Hello all,
> Here's something I would like to have some comments on. It's about an
> option to load config files at startup (e.g. a file for earphones (f1.cfg,
> vol=62, bass+treble somewhere around 5) and a file for home stereo
> (vol=81, equalizer flat) is what I use now. Beneath are my ideas about
> this, please feel free to comment, criticize, burn me to the ground, etc.
> I was thinking about start working on the autoloadconfig thingy again.
> Last time I tried
> adding a config option to show it or not show it, on the same screen as
> the resume screen.
> This introduced quite bulky code (e.g. when the resume screen is not
> shown, sometimes the
> autoloadconfig screen should be shown, etc.)
> The idea that I have is as follows:
> * link it to the resume screen, always. If people want an autoloadconfig
> screen, they won't
> care if the press-play-to-resume is on there, too. It won't hurt normal
> rockbox operation,
> * make it 'autodetect' f1.cfg, f2.cfg, f3.cfg, up.cfg, down.cfg files. And
> perhaps left.cfg
> and right.cfg too. A config option might not even be neccesary in this
> case, i.e. if rockbox
> would ship with f2.cfg and f3.cfg out-of-the-box, so people would see the
> option exist, and
> can delete the files if they don't want it.
> * if a .cfg file does not exist, then do the 'normal' resume screen action
> (=don't resume).
> This way a user can choose keys appropriate to him and his model, a
> recorder user can choose
> left/right too if he likes. The text at the bottom of the resume screen
> can be something like
> "Press key to load .cfg" (which is only shown when there are appropriate
> .cfg files)
> Maybe a config option will be neccesary to avoid confusion, or to make
> sure people know about this feature without reading the docs and without
> having to ship rockbox with a .cfg file. But is all this hassle and extra
> code and extra config space worth it?
Received on Thu Mar 31 22:50:06 2005
Page was last modified "Jan 10 2012" The Rockbox Crew