I solved this one I think. I noticed that the gears example is just as fast on each one.
So I looked and found that the button example uses timeouts while the gears uses timers. I found that if I just speeded up the timeout on the button from 10 seconds to 3 seconds for gtkglextmm it was just as fast as 10 seconds on gtkglext. And at 1 second it was faster. So it turns out to be something about how the timout is implemented in gtkmm and (perhaps how it interacts with other concurrent functions that are running. thanks, On 15:56 Mon 07 Jan , Stéphane Brunet wrote: > Hi, > > Could you try a profiling program to find out where the problem is ? > There are too many libraries involved to know where this difference > comes from. > > Stéphane > > Mitchell Laks a écrit : > > Hi, > > I just noticed that when I run the sample button programs that come with > > button.cc button.c button.pl > > > > gtkglextmm > > gtkglext > > Gtk-GLext > > > > the version written for gtkglextmm runs 1/2 as fast as the other two. Why > > is that? > > The jumping doughnut (torus) rotates at 1/2 the speed, ie 15 not 30 > > revolutions per minute on > > my workstation with amd64 and nvidia 6600GT graphics card. > > > > are all opengl applications that slow with gtkglextmm? i will try a nehe > > rotating texture square > > next and compare it to the glut version. > > > > Thank you, > > > > mitchell > > > > _______________________________________________ > > gtkglext-list mailing list > > [email protected] > > http://mail.gnome.org/mailman/listinfo/gtkglext-list > > > > > > _______________________________________________ > gtkglext-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gtkglext-list _______________________________________________ gtkglext-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkglext-list
