xbmc/xbmc — pull request #1701 by Montellese (2012-10-30 18:42:56+00:00)
Title: Restore possibility to type in the value field of a smartplaylist rule for browsable fields

During GSoC I extended smartplaylist rules to support implicit ORing within a single rule and field. For that I added the possibility to select multiple values from the list of possible values for a browsable field. Out of caution I removed the possibility to manually type into the value control of a browsable field because the user needs to follow a certain syntax to be able to specify multiple values which result in implicit ORing.
While this makes sense for operators like "is" and "is not" it doesn't make any senses for "starts with", "ends with", "contains" and "does not contain" where the user usually doesn't provide a fully matching value. Therefore we need to allow manual typing in the value control.

These changes add that functionality back. The syntax to define multiple values for implicit ORing is to seperate the values by " / " (the spaces are mandatory because some scrapers e.g. provide genres like "Thriller/Suspense"). If the user has manually typed a value which does not match any actual value and then uses the "Browse" button to view a list of available values, none of the values is pre-selected and selecting a value from the list results in the loss of the previously entered value.