Multiple Playlist Tutorial - Part 2

  The CD Label is now displays your playlist's information. 

When you apply a playlist the data will populate the playlist fields on the currently displayed label, along with any unassigned playlist fields.  This rule exists so that people who print out one CD and spine at a time don't have to take the extra step to apply the playlist to the spine label as well. 

The playlist is now saved in the current design file and becomes a local playlist.  

At this point it might be helpful to explain the basics of the playlist manager and how it works with the labels and playlist fields.  There are really three levels of data in SureThing:

1) Design: The first level is the text on the design itself.  Changing the data directly from the design area will not change the data in the associated playlist, or in the database.  Only that particular label's information will change.   If you later edit or change the local playlist the fields will be re-populated with the new playlist information.  The program will prompt you to be sure that you want this to happen: 


If you answer yes to this dialog, any changes you may have made at the design level will be lost.

2) Local: The second level is the local playlist(s).  These are listed in the Playlists in Document section of the manager.  Every playlist that has been added to a particular design will appear in this section.  Editing a local playlist will change the data on any label which that playlist has been applied to.   

3) Database: The third level is the playlist database which is independent of any one design file.  When you apply a playlist from the database the artist, title and track information are transferred into the design file as a local playlist (Playlists in Document) and the data will populate the playlist fields on the label.  Changes to the database playlist will only change the database entry, and will not effect the current local playlist or the actual design.