Add comment about its data type somethere/
There is no reason to put this into separate scope, the IndexMask only is reference container (still large to be accidentally copied). Memory usage is liner and only depend on the IndexMaskMemory.
I think this is important to process all points via index mask at once instead of relying on the curves, like issue with its fragmentation in #128325. Its also much simpler if case you just see…
You can do liternal the same thing by dragging the socket shape, and this works for all data types. But would be good to support this for properties outside of the node editor
Ah, stop. Idea was that for single element here is no neigboard, so you actually should count with starting from 0 rather than 1.
Not sure about this, but does this mean that lambda is instantiated for single/field of outputs as well as for input? So there is 6 instances instead of just 2\
Looks like mf::MultiFunction case.. At least, not sure if this is correct / worth it to combine kind simple computation of two values in one callback without explicit output.
Didn't check fix this changes looks correct, thanks!
This is correct fix, but should ge in separate PR, also into 4.3/
Create temporal const VArray<bool> cyclic = curves.cyclic(); outside of the lambda.
For help using Blender, please try one of the community websites: https://www.blender.org/community/
If you think you found a bug, please submit a new report and carefully follow the instruction…