Add method 0 for auto-select to check_for_collision_with_lists #2762
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
check_for_collision_with_lists
function had different behavior thancheck_for_collision_with_list
.By default in the non nested version of the function we use
method=0
which performs an auto-select that say:This auto-selection didn't exist in
check_for_collision_with_lists
and so would only ever use the selected mode, which by default was spatial hashing. However if the spatial hash wasn't available it would fallback to GPU collision, and only ever use the full CPU check if it was explicitly requested withmethod=3
. GPU collision is very costly for small spritelists and only makes sense with large spritelists.This adds the same auto-selection to each function.