FIXED: [2023.11600] OP Find DAT - Par Name + Par Value does not match toggle pars

What the title says, can’t find a way to make OP Find work with toggle Par filters.

Here’s an example toe:
OPFind_Toggle_Bug.toe (4.6 KB)

This is older than 2023.x, probably goes way back.

Thangs for the report.

This is logged for a developer to look into it.

Best,
Michel

1 Like

So, learning new things everyday…

Coming from the past, it was internally designed with on / off. If you use 'on' or 'off' (quotes if in expression mode, otherwise you can just type on or off) it does the trick for you?

This will be fixed however to cover the natural case of a boolean.

1 Like

That does it, I tried ‘On’ and ‘Off’ but didn’t try the lowercase variants :man_facepalming: … However, I will take this opportunity to inquire about the Active Cook parameter set to Automatic, using parameter filters does not seem to cook the OP automatically when the value changes, but I would argue that would be an expected behavior.

I’ll follow-up for the Automatic request.

With the wiki stating

Only cook / update the contents when the results would change.

I’d expect the DAT to update when you toggle on / off.

1 Like

The DAT now updates when you toggle on/off.
It was getting confused with the upper case ‘Active’.
As a workaround, you can turn off ‘Case Sensitive’.
This will be fixed in builds 2023.11650 and later.
Cheers.

1 Like

Awesome, thank you both!

1 Like

I don’t think this has been fixed. I tried all kinds of variation, but only on/off seems to work

Hi @The_NODE_Institute

Sorry about the confusion.

This will be fixed in the next branch we post, not in the current official branch.

Best,
Michel

1 Like