On 10/8/07, pondlife <[EMAIL PROTECTED]> wrote: > > > Option 2 will not be localizeable so it is IMHO a bad idea if we ship > with > > defaults and it would be even worse if we ship without defaults... > > Why do we need to ship with defaults? > > I'd just have it list the existing CFG files (as created/named by the > user). > Initially it would be a blank list (assuming we use some "cfg" directory, > otherwise "config.cfg" would be listed). > > -- > pondlife
It wouldn't be a problem for me to have a blank list but (new) users might find it rather confusing that the display just goes blank if you (for example) long press a button. But since it seems the resistance agains any custom menu is quite strong, I like this idea (with the possible increase in user confusion) more than the current screen (which btw isn't fully localizable anyway) .
