This runs counter to an intentional design decision in the code because it would mean a lot of allocation and garbage collection for that array as it's re-created and destroyed inside tight draw() loops. You'll notice that all the low-level functions in core are designed to avoid allocation wherever possible because they can lead to stuttering. A proper solution for this issue needs to minimize the use of new for a bunch of temporary variables.

@benfry That's fine; I'd like to replace the floats fillR etc with a final float[] fillColor that can be passed to calcColor, which would also return the color as an int in 0xAARRGGBB form, so that the color() functions would not need to pass the float[] array. Should I delete fillR etc., tag them depreciated but keep filling them, or leave them alone entirely? The same applies to stroke and others.
In other words I don't know whether third party code is expected to use protected methods/variables or whether it's okay to change them like this.

Messing with fillR would break all renderer subclasses (OpenGL in particular). The solution would need to work across all renderers and not break existing code.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.