Hi again, it's been a while! I implemented alphadraw() using the actual pixel values rather than just calling the canvas drawing operation. It calls canvas' getImageData() for each of the src, dst, and mask images every time it is invoked, which is relatively expensive. However, now that alphadraw() is used for almost everything, there is no reason to keep images as canvases. For now I'm still using a canvas and caching the getImageData(), but once my own memlayer(2) is working well enough that I can do away with the hack of positioning canvases with CSS to represent windows, I will be able to remove the canvases entirely.
Right now I'm working to remove corruption that results from drawing an image onto itself, which occurs when scrolling windows in rio. -- David -- You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code" group. To unsubscribe from this group and stop receiving emails from it, send an email to plan9-gsoc+unsubscr...@googlegroups.com. To post to this group, send email to plan9-gsoc@googlegroups.com. Visit this group at http://groups.google.com/group/plan9-gsoc. For more options, visit https://groups.google.com/d/optout.
