C++ is Greek or worse, Hebrew to me. Lazy as I am use Alea/C#.
// Rolf
One thing I don’t seem to get rid of is a grafted result with two items in the Output “F”. Where is that coming from? There should be only one bool array filter there.
I tried all kinds of things to get rid of the extra item but no go. If I cheat and simply flatten the output there’s a null item in the zero index position. < scratching head >
The suggested code also doesn’t actually retreive the DataAccess (DA) on a first compile. Not even if the RunScript method calls CurrentDataAccess everytime.
Another problem is that the UI/canvas freezes for very long if selecting the upper left Point parameters with the 100k points in. This happens even if the Solver is disabled. Why is this? When the “last resort” by disabling the Solver isn’t effective then we can end up in very deep trouble.
Eat bugs for breakfast? 
Point_Inclusion_Debug_RE2.gh (2.6 MB)
// Rolf
Because both you and the script component are assigning data to it now.
Ouch.
In addition to that, and I don’t know if I just have a bad day today but…, when I try to add another output A below F, just for testing, then there’s no output at all to the additional output;
DA.SetData(2, “Helloooo”);
Null. That’s all.
Feels like I should try restart my computer.
// Rolf