Suggestion: Option to set wrapping behavior
- Dominant language
- JavaScript
- Stars
- 15.5k
- Forks
- 663
- PR merge metrics
- No merged PRs in 30d
Description
## *What* is wrong?
When accessing surrounding pixel in on the y axis, which are out of bounds, it wraps to the other site of the texture, instead of failing, or similar. For example if you have a 200 x 200 texture, and want to access myTexture[200][0], you will get the value of myTexture[0][0].
At the moment, this only happens for the y axis.
## *Where* does it happen?
When accessing a value of texture on the y axis, when it is out of bounds.
## *How* do we replicate the issue?
See the explanation above.
## *How* important is this (1-5)?
2
## Expected behavior (i.e. solution)
This should be consistent for the x axis as well. Best, this is configurable.
## Other Comments
Contributor guide
Assessment
This issue has not been assessed yet.