Closed pFernbach closed 4 years ago
Actually the sampleContainer is already sorted at creation and everytime where the StaticValue is changed, so I removed this sorting entirely.
I did not find any way to enter setCollisionFree()
with a sampleContainer not already sorted, if I'm wrong you can close this PR.
In such case should not we remove entirely the sort parameter ?
Yes probably I just kept it for potential future cases, but I do not really see when it could be used
Instead of sorting the
limb->sampleContainer_
at each call tosetCollisionFree
, sort it when the Limb is first created.The sorting comparator used here only care about the
staticValue_
of each sample, which is constant once the database have been created so there is no need to sort it at each iteration.