#Broadway is apparently supported in #GTK again?
on 02024-01-31The ::button-press-event signal is how to be informed in #GTK that a mouse has been clicked. Similarly there are key-press-event etc.
The #GTK 3 porting guide explains how to change from expose-event from GTK 2 to draw in GTK 3.
The #GTK 3 porting guide suggests that you can make your life happier by drawing things with #Cairo instead of using GDK, since GTK 3 just uses Cairo, and there is no more GdkGC or GdkImage. Nearby it shows how to clip in Cairo to avoid overdraw.
The ::expose-event signal in #GTK, replaced with a ::draw signal in GTK 3.
#GTK 2’s drawing model. This kind of overview is missing completely from the GTK 3 manual. It explains, for example, that you get a GDK_EVENT_EXPOSE event when you need to redraw a region of a GdkWindow, which may contain an entire tree of widgets, and GTK+ then invokes the expose-event signal on the appropriate widget or widgets, and that GTK_DOUBLE_BUFFERED is turned on by default, but you may want to invoke gtk_widget_set_double_buffered(widget, FALSE) to turn it off, and that you can turn on GTK_APP_PAINTABLE on a GtkWindow or GtkEventBox in order to let you paint them instead, or you can use a GtkDrawingArea.
Example #Cairo code showing different things you can do with text in Cairo in #GTK. Part of a GTK #tutorial.
on 02015-08-05This is the function to draw a line of text in #Pango (and #GTK). It invokes draw_shaped_glyphs, which is private. It’s not mapped in lablgtk2.
this is the #Pango function to find out how wide #GTK thinks some text should be; it’s not mapped in lablgtk2.
on 02015-08-05apparently #GTK 3 no longer exposes low-level text drawing routines; instead you have to use fucking #Pango and #Cairo.
on 02015-08-05I didn't realize there was a #DirectFB port of #GTK!
on 02015-08-05The #GTK 2 reference manual.
on 02015-08-05