1
edit
Changes
→Release 0.3
: Ticket I filed for p5 while working on this ticket. [http://code.google.com/p/processing/issues/detail?id=594#makechanges #594] -[http://code.google.com/p/processing/issues/detail?id=601 #601]
: Other pjs tickets related to this one: [https://processing-js.lighthouseapp.com/projects/41284/tickets/1174-mandelbrot-and-histogram-ref-tests-are-failing #1174]- [https://processing-js.lighthouseapp.com/projects/41284/tickets/860-color-0-burns-through-non-transparent-background #860]-[https://processing-js.lighthouseapp.com/projects/41284/tickets/948-negative-opacity-values-give-incorrect-results #948]
* '''Issues'''
: On the way to fix this bug, I tried to compare it with how p5 handles this.
: To work with p5 code, I cloned it from [ http://code.google.com/p/processing/source/browse/trunk/ here] with the latest instructions at the bottom of [http://code.google.com/p/processing/wiki/BuildInstructions this page].
: Then I started to debug it on eclipse, with these [http://processing.org/learning/eclipse/ instructions].
: The result that I'm getting for the pixels from both p5 and pjs are the same. [http://minooz.wordpress.com/2011/04/06/once-upon-a-time-punch-cards/ Here] is a sample of these results.
: I thought it might be something with some charactersitics of pixels in p5 e.g. ''fillAlpha'', ''calcAlpha'',... for which I couldn't find any correspondent in pjs so far.
: Those characteristics where changed in ''pGraphics.java'':
:: line 5076:
* '''Helpful tips'''