Re: migrating gtk

Hi all; it's time for an update. On 2 February 2018 at 14:04, Matthias Clasen wrote: > Hey Carlos, > > we discussed gitlab migration for gtk here at the hackfest. Our > conclusions were as follows: > > * We want to migrate the git repository as soon as possible >

Fwd: double_buffered and scrolled_window

Hi all, After lots of years I finally got around to porting my widget GtkImageViewer to gtk3. After doing lots of reading of man pages, did I realize that i can turn off double buffering. I did it, and everything worked fine, except for one artefact. Once I turned it off, the scrolled bars of the

Re: double_buffered and scrolled_window

On 16 April 2018 at 10:19, Dov Grobgeld wrote: > Hi all, > > After lots of years I finally got around to porting my widget > GtkImageViewer to gtk3. After doing lots of reading of man pages, did I > realize that i can turn off double buffering. > I wonder what kind of

Re: double_buffered and scrolled_window

Hi Emmanuele and thanks for the detailed reply. Boy, do I feel like I flunked the widget writing class. :-) I'll take all your recommendations into consideration as time allows. I realize that gob is dead. I should be going to pure C instead. I can't even use the straight gob output, but have to

Re: double_buffered and scrolled_window

On 16 April 2018 at 11:15, wrote: > > Regarding, the gestures, is there a tutorial of how to use them? The > CustomWidgets tutorial mentions them, but then goes on to describe the > button and motion notify events. > https://wiki.gnome.org/HowDoI/Gestures - to

How to caught signal from the popup list of a GtkEntryCompletion

I have an application with a GtkEntry. As a feature of the program, I use key-press-event signals on this entry for GDK_KEY_Up, GDK_KEY_Down, GDK_KEY_Return and GDK_KEY_KP_Enter. But the I also would like to disable these homemade functions when the GtkEntryCompletion shows completion popup

Re: Scrolling to a GtkListBoxRow after adding it to a GtkListBox

On Sun, Apr 15, 2018 at 1:05 PM, "Matthew A. Postiff" wrote: Is the issue that the widget is not yet drawn, so it size/location coords are not settled yet? I originally thought so, but when it occurred it looked like it was actually be correctly getting scrolled to