This issue is a bit tricky; I'd appreciate it if you took the time to check and confirm or deny it. Don`t know if this is an actual bug or a by-product of how Evaluator works.
If you have a column using item.metadata
value to choose what value to display, and then you want to reference that column using Evaluator (e.g. for textual filters), item.metadata
will always be 'none'.
Steps to reproduce:
-
Preferably in a folder with few items, containing some images with an X resolution of 96 dpi, use a column that use
item.metadata
to decide the displayed value. You can use this column made for this purpose, showing the X resolution only for files recognized as images.
eval_col_test.opusscriptinstall (974 Bytes) -
Use the following command:
SELECT NONE SHOWHIDDEN
SELECT HIDEUNSEL FILTERDEF script match resx_test/ResX_test 96
normal filtering test.dcf (419 Bytes)
You can see that the filter retrieves the data correctly. In the script logs panel, we can see that all files are displaying item.metadata
to their correct value.
- Use this other command:
SELECT NONE SHOWHIDDEN
SELECT HIDEUNSEL FILTERDEF =if (IsSet("scp:resx_test/ResX_test")) return Match(Val("scp:resx_test/ResX_test"),"96","p"); else return false;
evaluator filtering test.dcf (539 Bytes)
Now in the script logs panel, we can see that all item.metadata
values are displayed as 'none', so there's no data available for that colum, and therefore, no matches.