First, i'd like to apologize for not actually submitting these as bug reports. I simply don't have the time, but since i've been using processing for quite a while, i thought i should at least try to help. In making my latest game, i've discovered a few bugs.
Processing 2.04/1.51 share these bugs on amd64 bit processor, both Win7 64bit and Linux Mint 64 bit.
1. OpenGL 'ellipse()' slows down the framerate, from which it never recovers. Amount of slow is determined by the size of the ellipse - pretty much any ellipse does it, about 200px is enough to turn a 60 fps sketch to 30 fps. Images, lines, and rectangles don't seem to have this problem.
2. Errors do not highlight the actual error like they used to. Cursor skips to the end of tab 2, and bracket highlighting is then disabled until you type a new bracket. Would be better not to attempt to highlight error at all, as it moves me to a different tab than the one i was working on.
3. Minim is unpredictable in linux and usually freezes the program whenever minim is asked to play a new track(not always, but most of the time). Problem does not appear in windows.
4. 64-bit Linux exports from windows do not work, only work if they were exported in linux.
5. Text is randomly blurred. If designating textbox size, usually line 2 is blurred. When making single text lines, about 1/10 lines is blurry. In the above picture, you can see that the 'options' button is blurred.
It's okay if the mods wish to delete or move this post. As i said, i only want to help. Besides the time factor, i don't even understand how bug reporting works and probably won't learn. The reason i use processing is that it's pure programming. From makefiles to system path to setting up display and memory usage - these are all things i can skip and go right to game design, in processing. That's why i use it!
This game took about 10 working days to make, from scratch to final bugfixes, including sound and graphics. I can't imagine any development environment matching that speed.
1
