|
You found a bug, introduced in 0.7.55. Searching incorrectly checks the new tristate preference, reversing its meaning. Thus, searching in tristate columns (ones with undefined values) incorrectly makes undefined and false into equivalent values.
A fix has been submitted, and should be in the next release.
Until the next release, the only workaround that I can think of is to create another custom column 'made from other columns'. Use {#boolcol} as the template, replacing #boolcol with the lookup name of your column. Set the search type to text. Search for 'Yes' to see true values, search for 'No' to see set-to-false values, and search for false to see undefined values.
|