Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1043902" data-attributes="member: 18896">They already do, and I help maintain the primary expression. It's the one that parses my entire collection and follows the scene defined standard formatting of:&nbsp;&quot;Show Name - S01E01 - Episode Title.ext&quot;&nbsp;Supporting the millions of other combinations that users create is a developers nightmare. Still extra expressions are added to account for a few alternative schemes, but it is impossible to account for all. If enough users on the &quot;Express/Rules Exchange&quot; vote that new expressions work fine for them, then they can be added to the default. The problem is that a new expression for one user can lead to false positives for another. This is why new expressions are only added with extreme caution.&nbsp;I did recently help create an expression that solves acronym show names, and that one is now default and part of the installer. But once again extreme caution is used. You might never see that expression, until you hit RESET inside the expression list, because by default the installer doesn't upgrade expression out of fear you might have made custom modifications and it does not want to break them.&nbsp;So verify first you have the current expressions in use right now by using RESET, test again and check the Exchange thread to see if an expression already exists for your non-standard naming scheme. Then if you know a certain expression works, and it is not default, do all the testing to ensure it will not lead to false positives for the 99% who do use standard naming schemes.</blockquote>

[QUOTE="RoChess, post: 1043902, member: 18896"] They already do, and I help maintain the primary expression. It's the one that parses my entire collection and follows the scene defined standard formatting of: "Show Name - S01E01 - Episode Title.ext" Supporting the millions of other combinations that users create is a developers nightmare. Still extra expressions are added to account for a few alternative schemes, but it is impossible to account for all. If enough users on the "Express/Rules Exchange" vote that new expressions work fine for them, then they can be added to the default. The problem is that a new expression for one user can lead to false positives for another. This is why new expressions are only added with extreme caution. I did recently help create an expression that solves acronym show names, and that one is now default and part of the installer. But once again extreme caution is used. You might never see that expression, until you hit RESET inside the expression list, because by default the installer doesn't upgrade expression out of fear you might have made custom modifications and it does not want to break them. So verify first you have the current expressions in use right now by using RESET, test again and check the Exchange thread to see if an expression already exists for your non-standard naming scheme. Then if you know a certain expression works, and it is not default, do all the testing to ensure it will not lead to false positives for the 99% who do use standard naming schemes. [/QUOTE]

Verification