On Wed, Dec 22, 2010 at 3:16 PM, Paul Davis <[email protected]>wrote:
> On Wed, Dec 22, 2010 at 3:04 PM, Brian Phelps <[email protected]> wrote: > > > I take it there is no way to practical way to fix this by creating some > > custom widget? > > its more the case that there is no reason to think that existing > widget implementations actually have a problem that needs fixing. > I know that I can do the same thing with mozilla firefox using javascript but with cached pixmaps and it is instant. There is something strange going on with how many widgets are handled in GTK. 1/4-1/2 a second to update a screen is a bit slow, considering the x11perf results say it can be done MUCH faster. Yes firefox does this faster with javascript and pixmaps than GTK. I find that strange. I am just trying to figure out how I can do it with my particular GTK code. > > > Also yes I have tried turning off double buffering. It makes no > difference. > > did you try different themes yet? these can have a VERY dramatic > impact on drawing speed. my main application is more or less unusable > on certain backends with certain themes, because the themes are so > slow and use functions that are not efficiently implemented in the > backend > Maybe the theme is slowing the gtk version, but I tried it with pixmaps instead of buttons and it was slow too. It seems slow with the default theme too. Same hardware is tons faster using firefox+javascript+pixmaps
_______________________________________________ gtk-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtk-list
