Hey there,
I have encountered some mysterious behaviour when working with expressions. It has to be said my knowledge of how that works is patchy at best, but I really believe its not just me.
I have noticed that the expression I had used in the rename-files-from-properties window didn't work anymore after I updated to the latest build some days ago. Furthermore, I have found that the exact same expression that works for a view scheme I made, doesn't work if copied to the 'filename rule field' in the 'rename files from properties' window.
The expression was FormatBoolean(IsMissing([Release Code]), well-known, missing). Its output in the rename-files-from-properties dialogue field is always "well-known" whether the track had an associated release code or not.
If tried many different things in order to get an "if, then, otherwise" type of command but I couldn't get it to work. I even tried copying expressions from the wiki-page and they wouldn't work either.
For Example:
What 'the rename file from properties' function outputs when entering
if(isempty([Disc #]), nuthan, [Disc #])
is "unknown disc #" if there is no value for 'disc #'.
Should not the value be "nuthan" in the case that the number is unknown?
Eventually, I made it work using the following command.
if([Disc #, 0]=[], /([Type][Disc #]/), ) [Artist] - [Name]
test false, true,
Shouldn't it be:
test, true, false, ?
There is something strange there, isn't it?! ?
Author
Topic: Expressions going mad (Bug?) (Read 770 times)