This bug is really annoying. I have reported it via e-mail in December 2013 after upgrading from Disc Cover 2, then again in August 2014. It's been confirmed by staff, yet nothing has ever happened to fix it.
So much for "support".
But fear not, fellow users, the fix is here!
Luckily the bug affects just the "Text Data" import section, not "Music", "Pictures" or "Video".
The fix itself is pretty simple. Either it can be done via Terminal (I'm skipping that for now, as I'd have to figure out the exact command yet), or with a 3rd party app. Some of those apps are available for free download, so it can be done at no cost.
1) Under the "Text Data import", import a random folder, or a random plain text file in order to access the "Format: Custom" editor.
2) Create all custom formats that you'd eventually like to use. You cannot use them yet, but they will be already saved for future use, and we'll enable them in a minute.
3) Quit Disc Cover 3.
4) Open the file:
Code: Select all
with an app that can read binary plist (XML) files.
That's for example:
If you're comfortable enough to read unformated XML files, you can also use an advanced text editor like TextWrangler (discontinued) or its successor, the unregistered version of BBEdit: http://www.barebones.com/products/textwrangler
5) E.g. with PrefsEditor, search for "disccover3", then open the ID "com.belightsoft.DiscCover3".
6) Expand the item (line) named "CustomImportFormats" (type "Dictionary") by clicking the triangle on the left.
7) You'll see a line named "data" (type "Array"). If you expand it further, it contains one or more numbered "Items"; those are your custom formats.
the "data" array to "folder
9) Save. (In PrefsEditor saving is actually called "Sync", but the effect is the same.)
10) Relaunch Disc Cover. Upon importing a folder or a text file, your custom formats should now be available from the dropdown menu.
You can actually create your custom formats directly by creating and editing the arrays in CustomImportFormats. All you need to know is the syntax (it becomes obvious by inspecting your already existing formats), and the abbreviatons used by Disc Cover. You may need to create a couple of "test formats" first with all available Field Names to see which abbreviations are in use in the Text Data section. There's e.g. "#FS" for "file", "#FF" for "folder", "#FS" for "size", etc.
That's about it. Let's hope the Belight developers get their act together and fix this bug at last, all that without charging us an upgrade fee for a v4!