Re: Problem with component image capture with Component.printAll()

[Thomas Fitzsimmons]

On Sat, 2004-07-24 at 13:58, Jeff Myers wrote:
> Greetings All,
> 
> I'm attempting to test out Classpath's AWT support, specifically in
> the context of component image capture capability necessary to support
> the Eclipse Visual Editor project.  Classpath's Component.printAll()
> method is returning a badly garbled image (with Classpath 0.10 running
> via jamvm).  Attached is a simple testcase of this issue.  Any help
> resolving this issue would be appreciated.
> 

I looked at this briefly.  What you're seeing is the result of painting
uninitialized image data.  To solve this, we'll need to have GTK not
only paint widgets on its native windows, but also into the graphics
object that we pass to the peers' paint methods.

For example, see GtkComponentPeer.paint.  We'll need to call a native
method there that calls GTK to paint the widget into g's buffer.  I
don't know how to do this, but I'm pretty sure it's possible, since I've
heard Mozilla does something like this to render its native-looking
widgets.

Can you file a bug in GCC bugzilla under the AWT component, and attach
this test case?

Thanks,
Tom