You're right, I have to try and make measurements myself whenever possible, it's not something that comes to my mind instinctively.
However these were simple questions and I didn't want to reinvent the wheel ;)
Ok ended up doing two tests and here are the results. I hope it will come useful to someone. Personnally that's the kind of good practices I'd like to see listed somewhere ^^
1/
- The "Set Color" appearance action is not CPU intensive (apart from the very first draw call when the action is used). It is thus entirely safe to use on a lot of spritefonts at the same time and is a convenient way to change color.
- The "SetColor" effect is still very CPU intensive. It WILL bump the Draw Calls in a continuous manner if there are a lot of sprites using it.
If you need to use it, consider disabling it as soon as you don't need it anymore.
mediafire.com/file/qz9t8ps9czt172y/TestSetColor.c3p/file
2/
- Yes, several picking actions appear logically to be more CPU intensive (on the Event side) than a single "grouped" picking action. I'll try to use this method of picking as a good practice from now on.
mediafire.com/file/2uqco0qx99nphkz/TestPicking.c3p/file
See you