Summary: | ConvolveOp troubles | ||
---|---|---|---|
Product: | classpath | Reporter: | Norman Hendrich <hendrich> |
Component: | awt | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bug-classpath, david.gilbert |
Priority: | P3 | ||
Version: | 0.92 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Known to work: | ||
Known to fail: | Last reconfirmed: | ||
Attachments: | Proposed patch |
Description
Norman Hendrich
2006-07-18 16:42:09 UTC
Created attachment 11913 [details]
Proposed patch
I've attached a patch that should fix (1) and (2), but is unlikely to improve the performance of this class. Please give it a try. (In reply to comment #2) > I've attached a patch that should fix (1) and (2), but is unlikely to improve > the performance of this class. Please give it a try. Thanks! Confirmed; the patch seems to fix (1) and (2). That is, my application now survives the filter() operation, and the results of simple kernels look ok. However, lacking nice testcases I didn't check the output images for correctness. For some reasons that I don't yet understand, trying to paint() the result images is extremely slow (about 3 seconds per repaint for 640x480 ARGB with ARGB DirectColorModel) and makes my app completely unuseable. For example, opening a menu triggers a few repaints, each of which takes 3 seconds... Still, I'm closing this now. |