problem to send a notification.

Hi everybody, I have write the following code but their is no way to send a notification even if it's say that isn't guarantee that something will happen in the documentation concerning notifications with gtk/gio. ```C #include #include #include #define DEBUG_FUNC_MARK do {

Re: Debugging propagated events

In Gtkmm (C++) you can overload the on_draw() function with your own. This might give you a foothold in the on_draw() routine that is called after a redraw event occurs. I guess in GTK you would have to connect a callback function to the "draw" signal. Might help.?? jim... On 2016-11-28

Re: Debugging propagated events

Hi, Why don't you link against the debug version of the library so that it shows you the complete stack? It will give you some extra clues on why the segfault is happening. Regards, Alfonso Arbona On November 29, 2016 6:17:05 AM GMT+09:00, zahlenm...@gmx.de wrote: >For a custom widget I have a

Re: Debugging propagated events

This was one of the first things I did. Debug compilation option, debug CFLAGS, no stripping - without a change. The backtrace only shows 3 lines, my draw function and two from libc. The faulty address is not null. But the segfault happens after the return where all local variables are no longer

Debugging propagated events

For a custom widget I have a draw function. I do some drawing there and when I am finished I return FALSE to let the parent draw. Immediately after the return statement I get a segfault. gdb's backtrace only shows my draw function and an address I cannot associate to any object. Are there some

Re: g_error_free on a null pointer

Hi; On 28 November 2016 at 18:48, Alex Henrie wrote: > Can I get some feedback on my patch for > https://bugzilla.gnome.org/show_bug.cgi?id=774738 ? > > If this bug is not going to be fixed then I'll make sure to put null > checks before calls to g_error_free, but if

g_error_free on a null pointer

Hi, Can I get some feedback on my patch for https://bugzilla.gnome.org/show_bug.cgi?id=774738 ? If this bug is not going to be fixed then I'll make sure to put null checks before calls to g_error_free, but if it's going to be fixed soon then I won't bother. -Alex

Re: FOSDEM Desktops DevRoom 2017 CfP

Hi everyone, We haven't received a lot of submissions so far, the deadline is next Monday, don't wait too much for submitting a proposal :) Cheers, Christophe On Sat, Oct 22, 2016 at 08:16:33PM +0200, Christophe Fergeau wrote: > Hello, > > Here is the Call for Participation for the Desktops