Come on, Cad, stay calm. I’m sure many users will find these features useful. And if you don’t, you don’t have to use them, do you?
The “allow Extra PFL” setting in the config will of course be respected. If you switch it of, there will be not PFL tab. Just like before.
I know many people from German community radios who prepare their show as a sequence of music and voice tracks, and then record the automated playlist, send the audio file to the station.
(Most German states don’t allow community radios to do live broadcasting, every show must be pre-produced.) The ability to render the playlist will be useful to these people. Of course, it’s not an essential feature for an automation software, but at least a neat gimmick.
Some background on the playlist: The component I am using now (Virtual Treeview) is much more flexible than the native Delphi components, including TDrawGrid, which is used in mAirList 2.0. For example, it allows resizable columns, drag & drop between multiple mAirList instances and so on.
In principle, Virtual Treeview provides a tree view with multiple colums. That is, if you use a flat item hierarchy (only one level of nodes without any childs), the “tree view” will look rather like “list view” or “grid”. At first, I will make the new “Playlist Treeview” look exactly like the old v2.0 grid. Then, we can think about how to take advantage of all of the features of Virtual Treeview. One idea is that, if you have specified a comment on a playlist item, to create a child nodes containing that comment. Then the user can decide which comments to show or not to show by expanding or collapsing the node. This is more flexible than the current global “show comments” option. Of course, you can still make all comments visible at the same time by expanding the full tree.
By the way, the same component is already used in various places in mAirList 2.0: In the Event Scheduler, the browser (all of the directory/database browser windows are descendants of Virtual Treeview), … The playlist is the final piece of the puzzle.
Ron, you’re right, all of the settings are stored in the ini file, which is only read by the main program, but never altered or rewritten. If you protect mAirList.ini (and possibly skin.ini and/or layout.ini), your presenters will not be able to make any permanent changes to the config.