1
edit
Changes
no edit summary
Monday July 19th<br />
* Today I fixed problems in tickets [https://processing-js.lighthouseapp.com/projects/41284/tickets/752-arraylist-is-missing-setindex-value 752], [https://processing-js.lighthouseapp.com/projects/41284/tickets/760-dont-assume-moz-attributes-exist 760], [https://processing-js.lighthouseapp.com/projects/41284/tickets/764-pexpand-doesnt-need-a-temp-array 764] and [https://processing-js.lighthouseapp.com/projects/41284/tickets/765-parraycopy-needs-to-be-fixed 765]
Wed July 28th<br />
* I fixed an odd pixel that was slipping in between lines split on a string with newline characters. The extra pixel only existed using TOP, BOTTOM, and CENTER on the y axis. Basically, everything cept BASELINE, which was default... The problem was due to using the text size, instead of using text ascent, which is the same size for smaller fonts, but as the font gets larger, the gap is more noticeable.
* Noticed I totally overlooked the 4th and 5th parameters of text, which are height and width. This also needs to account for text leading using newlines OR spaces that push the text onto the next line. There is also a few pixel padding in the p5 version from the top of the box, to the first bit of text, which is dependent on the size of the font. I am not yet sure where they get this number, but I am looking through p5's source. The last final problem in textLeading() has to do with the number of pixels being padded between newlines and multiple lines.
[[category:Summer 2010 July]]
[[category:Scott's Work Log]]