How to create a faster/more accurate image alpha check mouse hover function

[zorg]

I have no intention starting an edit war on the wiki, but in my opinion, the bit about non-interpolation made sense to me; maybe not next to the values though, so i can only say that there could be people out there who'd view that bit of information as relevant, so it'd probably make sense at least mentioning it somewhere on the page.

Edit: Also, "value" in that context may be a bit vague (even if you specified it as x and y values); i'd vote to use "index/indice(s)" instead.
I edited the [wiki]SoundData:getSample[/wiki] article to match yours, but with the above extras added in.

[airstruck]

I have no intention starting an edit war on the wiki, but in my opinion, the bit about non-interpolation made sense to me

I thought that saying the inputs were floored would be enough to indicate that outputs weren't interpolated, but I see nothing wrong with being even more specific.

Edit: Also, "value" in that context may be a bit vague (even if you specified it as x and y values); i'd vote to use "index/indice(s)" instead.

That was the terminology that was already there; it seemed clear enough to me. The part with the "coordinates" wording was copied more or less verbatim from a commit message.

The wording on the getPixel page is: "Gets the color of a pixel at a specific position in the image." So maybe "position" is better than "value." This is distinctly different from "index," and more descriptive of what actually happens. The pixel at position (3.5, 3.5) really is the exact pixel who's upper left corner is at position (3, 3); geometrically speaking that position is smack in the middle of that pixel. In fact, taking the "position" wording literally, it's almost redundant to say that inputs are floored or outputs are not interpolated.