Re: Musings on the proper use of g_error and GError

On 9/2/06, Edward Catmur <[EMAIL PROTECTED]> wrote: > On Sat, 2006-09-02 at 13:19 -0400, Philip Kovacs wrote: > > Looking at the glib code itself, e.g. in gmem.c: in the g_malloc() > > function, > > if the memory was not allocated as expected, glib does this: > > > > g_error ("%s: failed to alloc

Re: Unsolved clipping problem

>But when you let go of the slider, the windows look OK? Yes. >I don't think there is any problem then, surely it is understandable that while >scrolling there might be temporary display artifacts? You wouldn't say that if you could see how ugly it looks on my system ;-) >>> Do you have a scr

Re: Musings on the proper use of g_error and GError

On Sat, 2006-09-02 at 13:19 -0400, Philip Kovacs wrote: > Looking at the glib code itself, e.g. in gmem.c: in the g_malloc() > function, > if the memory was not allocated as expected, glib does this: > > g_error ("%s: failed to allocate %lu bytes", G_STRLOC, n_bytes); > > Clearly this is not a

Re: Unsolved clipping problem

Tintin72 writes: > Even if I remove the line: > gtk_box_pack_start(GTK_BOX(myApp.pScrollBar), myApp.pDrawArea, TRUE, TRUE, > 0); > the clipping effect occurs just the same. Of course it does. gtk_box_pack_start() notices the first paramter isn't a GtkBox, so it returns immediately without do

Re: Unsolved clipping problem

>> Do you mean that even after you stop moving the slider your program looks >> wrong? > No, the clipping effect occurs while I move the slider. But when you let go of the slider, the windows look OK? I don't think there is any problem then, surely it is understandable that while scrolling t

Musings on the proper use of g_error and GError

The glib documentation on error reporting is very specific on differentiating between runtime recoverable errors and programming errors: http://developer.gnome.org/doc/API/2.0/glib/glib-Error-Reporting.html Of interest to me is the rather strong statement that: "... the |g_error()|

Re: Unsolved clipping problem

>This is a *run-time* warning. Ok, but the pb remain the same. Even if I remove the line: gtk_box_pack_start(GTK_BOX(myApp.pScrollBar), myApp.pDrawArea, TRUE, TRUE, 0); the clipping effect occurs just the same. I'm wondering if GTK is really optimised for Windows environnement. I didn't find

Re: Unsolved clipping problem

On Thu, Aug 31, 2006 at 05:01:59AM -0700, Tintin72 wrote: > > >gtk_box_pack_start(GTK_BOX(myApp.pScrollBar), myApp.pDrawArea, TRUE, TRUE, > 0); > >a GtkScrolledWindow is not a GtkBox. This line causes the warnings: > >GLib-GObject-WARNING **: invalid cast from `GtkScrolledWindow' to `GtkBox' > >G

Re: Unsolved clipping problem

Thanks for your reply. >Do you mean that even after you stop moving the slider your program looks wrong? No, the clipping effect occurs while I move the slider. >Do you have a screenshot? http://web8.free.fr/images/pbClipping.gif >I can't see any problem like you describe with your test prog