There is already an option to not show Save buttons in the PFL Cue dialog. It seems logical to also have a new Miscellaneous option of Extra PFL: Show Save buttons in dialog (default ON). This would not be applied in mAirListTag, of course (!), where the Save buttons will always be displayed.
Partly because in v2.1, Torben will be moving ExtraPFL to the Properties dialog ;), and also following the same thinking as above, I further suggest a new Miscellaneous option of Show Save buttons in Item Properties dialog (default ON).
These would also address Ron Stanley’s request for a ‘locked down’ mAirList, where a presenter cannot save/overwrite (e.g.) MMDs or MP3 file tags.
Good idea. There should be distinct “allow to save to MMD”, “allow to save to file tag” and “allow to save to database” options, though. Saving locally to the current playlist should always be allowed.
Due to the way the Extra PFL and Properties dialogs are managed at the moment, I will not be able to introduce these options in v2.0, but I will provide for them in mAirList 2.1 (where all Properties dialogs are created at a central location in the source code, and it’s easier to pass options to them.)
I have not got my head around all the tags and MMD files yet
OK, Ron. When you change the Properties of any Playlist item, or set any cue points, you can choose to save your changes in up to four places:
Local means: write the changes internally to this Playlist only, don’t change any MP3s, MMDs, etc. The changes will be lost unless you later save the Playlist or the Desktop (MLP or MLD).
File tag means: write the changes to the ID3 tag inside the MP3 file, or the equivalent if it is a FLAC or OGG file (i.e. modify the audio file).
Metadata means: write the changes to the related MMD file, and create a related MMD file for this audio file if the MMD does not already exist. The audio file is not changed.
Database means: write the changes to the iTunes, eldoDB, or radioDB2 database I set up in Configuration. The audio file is not changed.
Obviously (?) you can only use option 4 if you have a SQL database configured in mAirList (an ‘on-the-fly database’ does not count).
if it would limit the fiddling potential then it had my vote!
In two words: definitely yes!
PS: There is now a page of all the Actions/Commands in the Wiki: I think it was you who asked for this, Ron?