> What is the exact bug report? I think this guy talks about the repainting problem I've seen when I tried to run AWT/swing applications on my N770. Even on the native side the expose-events were never received although it worked with a small gtk-testcase I created. This is the only problem which could be at least a bit matchbox related - maybe classpath's AWT peers set some hints that don't work. Could also be a broken version of GTK deployed with the N770. lg Clemens This is just my private opinion, I respect the work of everybody who has ever contributed to classpath. I always found the GTK peers disgusting, tons of effort, code, binary size and bugs just for supporting native l&f. And thanks to GTK broken from time to time with each new GTK release. My favourite would be a java-only implementation of x-protocoll based peers so that not even a single line native code would be needed (ok, maybe for the shm stuff) - widgets could be painted using swing like SUN now does with their XAWT. However just an opinion and (for now) too little time to do it myself. Thanks for doing all the work, its great to see how far classpath has come. > What "it" doesn't work when run with > Matchbox as window manager? If you have a small source code example that > works normally with other window managers, but doesn't with Matchbox > that would help. I tried some of our demo programs under matchbox and > they seem to work fine. Matchbox just make the windows very big (only > one window on top allowed it seems). But that didn't really seem to > break anything that I could see. > > Cheers, > > Mark > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > > iD8DBQBEImCAxVhZCJWr9QwRAocFAJwJUdojjVGANhDRrbYUKWBkr7FmEACeKCOs > QvGXwTA1I+kp9s9A6lo8gx8= > =sVGz > -----END PGP SIGNATURE----- > > >
