Rockbox Development > Feature Ideas

config per directory?

<< < (7/13) > >>

Llorean:
What happens if you put a new audiobook on, but forget to include a local .cfg to turn shuffle off? Or want to hear an album in order for once, but it has a local .cfg that turns shuffle on?

Really, the best way to handle it is to be responsible yourself, and maybe use the quickscreen to quickly toggle shuffle on/off as needed.

oayz:
If current directory doesn't have local cfg than default should be used (see my pseudo code).

I completly agree with you - this a feature most people including me can live without. Yet it does provide tremendous flexability. BTW, as I just learned from you from another thread CFG files currently can only be stored in the root ...

Llorean:
.rockbox is not "the root", and .cfg files can be stored anywhere, it's just that one option that only shows them within a certain folder.

It sounds like your folder-specific config files needs to have two values for every option then, one for "this folder's choice" and one for "the overall choice." Basically, it needs to treat them not like normal cfg files - it can't actually change the value of the option, just cause a temporary override when that folder's played that will be reverted at the stop of playback or when anything in any other folder is played.

oayz:
Well no, that wasn't my intent. I suggested to keep a pointer to global CFG - either default or the one user manually loaded. This CFG will be reloaded every time we exit a directory with local CFG thus restoring "original" settings.

Of cause logic may be different but the intent is simple:
- keep CFG load/parse/apply as it is now
- in directories with no local CFG keep current RB behavior

It's not fully thought thru proposal - some may suggest different (more complex) bahavior in directory tree. For example if directory BOOKS have local CFG it may propogate to sub-directories.

Thanks for correcting "root" and yes I now remember that we can browse files and click on CFG anywhere.

Confuseling:
@ soap and oayz

Just to clarify, I'm not arguing that in the long run, if the feature were fully developed, it would be of most use to audiobook / podcast users. I'm just saying that an initial form of it, hard disk spinning up warts and all, would be of clear use in this case. Given that it would be transparent, and have to be consciously turned on, I see no harm in making a useful but limited feature, and incrementally perfecting it to the point where it would be usable on an album by album basis.

The best is the enemy of the good, and all that.

@ Llorean

The case where you've got a config file in a directory and want to override it is an interesting one. You could maybe have three potential levels of settings; global settings, loaded as per now from a cfg file, local settings loaded because they're specified in a particular directory, and current settings if you adjust anything on top of that - discarded once you've left the directory again. Perhaps, ultimately, it would make sense to give the local / current ones an icon, or colour code them, in the settings menu.

It might also be nice to have a way to update local cfg files with new values. So if I went into a directory, then adjusted any parameters that were already specified in that directory's config, I could browse to the settings file and write them back with an 'update from current settings' or something from the context menu.

Navigation

[0] Message Index

[#] Next page

[*] Previous page