Thank You for your continued support and contributions!
Maybe simply add a good configuration in the root folder and call it "configuration.cfg".
Speaking of the "magic Rockbox folder" - is there a good reason why it's not set to "hidden" by default? Is it there so users can reset Rockbox easily?
We don't want to ship default config.cfg files - that will overwrite the user's current settings...
My thought was that there could be a default.cfg and a current.cfg. If current.cfg does not exist, default is used, but user's settings are stored in current.cfg instead. So, a clean install gets default.cfg, but user settings are never overwritten because current.cfg isn't included.Then you can easily package target-specific settings, that way.
Quote from: Spug on January 24, 2007, 08:55:17 AMSpeaking of the "magic Rockbox folder" - is there a good reason why it's not set to "hidden" by default? Is it there so users can reset Rockbox easily?It is hidden on all *nix-like systems (since it starts with a dot) and on the rest it can't be set hidden since then the hidden bit is a feature of the filesystem and not something we can ship in a zip file.
Page created in 0.219 seconds with 21 queries.