Re: Should gtk_widget_draw be un-depreicated?
On Fri, 2009-12-04 at 15:01 -0600, Harry Coin wrote: If there is a non-deprecated way to start a timer as soon as an image is known to be drawn without using gtk_widget_draw I'd need to be educated about it. If not I think there is a good argument to not deprecate gtk_widget_draw. Sounds like a very special use case. Have you tried starting your timer when the first expose-event is fired after you set the image? Regards, Thomas ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: Should gtk_widget_draw be un-depreicated?
Il giorno Fri, 04 Dec 2009 15:01:25 -0600 Harry Coin hc...@quietfountain.com ha scritto: The only answer I can think of to retain the ability to time most accurately, starting the moment that the image has been drawn is to use gtk_widget_draw right after setting the pixbuf. If gtk_widget_draw() is working for you, why don't you pasteadapt its code in your application? The implementation is quite trivial: http://git.gnome.org/cgit/gtk+/tree/gtk/gtkwidget.c#n3811 Ciao. -- Nicola ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: Should gtk_widget_draw be un-depreicated?
Thanks all. I'll just do the gtk_window_process_updates and that is that! Nicola Fontana wrote: Il giorno Fri, 04 Dec 2009 15:01:25 -0600 Harry Coin hc...@quietfountain.com ha scritto: The only answer I can think of to retain the ability to time most accurately, starting the moment that the image has been drawn is to use gtk_widget_draw right after setting the pixbuf. If gtk_widget_draw() is working for you, why don't you pasteadapt its code in your application? The implementation is quite trivial: http://git.gnome.org/cgit/gtk+/tree/gtk/gtkwidget.c#n3811 Ciao. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: GtkGLExt (was Re: Gtk 3.0)
Dear Emmanuele, yes. and that, apart from games and scientific/technical applications, it's not at all common. the amount of code using OpenGL is relatively limited (hence niche) compared to the rest of applications in the GNOME stack (or even in the whole Linux ecosystem); it's *usage* is limited, not the size of the codebase. If you go to Amazon and search for OpenGL books, you get this list with 2607 (!!!) results: http://www.amazon.com/s/ref=nb_ss?url=search-alias%3Dstripbooksfield-keywords=openglx=20y=19 Many of these books have been published in the last 5 years, some in 2008 and even 2009. The fact is, the OpenGL community is much larger than our GTK community. If scientific/engineering applications are a niche in the GTK world, that is not a OpenGL weakness, that is a GTK weakness. We must atract more scientifc/engineering applications for Linux and GTK, because this is exactly the kind of stuff that enterprises and universities are demanding. If we have fantastic operating systems and desktop environments in the free software world, but most of the scientific/engineering aplications only run in Windows/Mac OS X, people will be forced to use them, even if they would rather prefer to use Linux/BSD... I have many friends in this situation... Cheers, Carlos ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: GtkGLExt (was Re: Gtk 3.0)
On Sat, Dec 05, 2009 at 04:22:36PM +, Carlos Pereira wrote: We must atract more scientifc/engineering applications for Linux and GTK, because this is exactly the kind of stuff that enterprises and universities are demanding. If we have fantastic operating systems and desktop environments in the free software world, but most of the scientific/engineering aplications only run in Windows/Mac OS X, people will be forced to use them, even if they would rather prefer to use Linux/BSD... I have many friends in this situation... I'm afraid you explain it from your viewpoint. But looking at your reasoning from the `desktop' viewpoint there are troubles. 1) Objective. There will never ever be a scientific `killer app'. Every little branch of science, or even an individual scientific problem, has specific needs. Hence the applications are inherently scattered and each individual app is used only by a small group of people. Even the `universal' commerical tools such as Matlab are far from being universally used [among scientists]. This makes hard to see sci/eng apps matter *at all*. 2) Subjective. Do your graphs have round corners and include the user's IM status? Can your data acquistion software synchronize the data with an iPod? Are your reports summarized to 140 characters and sent to Twitter? No? Does your app help people with some difficult to understand and much more difficult to solve problems instead of facilitating idle chit-chat while consuming power for visual effects? Ah. You are such a loser. Go away. Regards, Yeti ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
