The result I expect is that the bottom right X would be cyan on a blue background (white X tinted green then added to blue). What I see is a white X on a blue background.
I have a physics simulation application that does a significant amount of math and a moderate amount of drawing.
When I export it to a Windows application and run it, I see about a 300% performance increase over running it straight from processing.
I see the same when I compile and run the generated source files in Eclipse (which I did for profiling).
When the project is run from within the Processing IDE, what is the Processing environment doing that is causing such a large performance hit and how can I stop it from doing whatever that is?
It's especially important to me because a client specifically tasked me with optimizing the performance of this application, but the client also wishes to run it from within the IDE.
Is it safe to create and/or draw on a JAVA2D PGraphics context in a different thread than the PApplet's main thread?
If creation on another thread is allowed, is it safe to access a PGraphics in a different thread than the one it was created in?
The general question is: does PGraphics use any thread-local resources that would make it unusable in a thread other than the one it was created in?
Edit: Synchronization is done external to the PGraphics, I'm not concerned about general thread-safety of it, just making sure there are no thread-specific resources allocated (e.g. in wgl a context must be used only in the thread it is active in).
