Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C582E2.35F2BB52" Subject: Suppressing Gdk Warnings Date: Thu, 7 Jul 2005 11:54:12 +0100 Message-ID: <08274F3CA42017478C1A9114E2B186B632B8D2 at axiom1.cambridge.internal> Thread-Topic: Suppressing Gdk Warnings Thread-Index: AcWC4jXbRKPbxTtVRieAb4ovHVx8Pg== From: "Matthew Lakin" To: This is a multi-part message in MIME format. ------_=_NextPart_001_01C582E2.35F2BB52 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi there, =20 I have an application which uses Lablgtk2 under Windows XP. I have run into a known bug in GTK (http://bugzilla.gnome.org/show_bug.cgi?id=3D137796) which causes errors of the form: "(camlprog.exe:1116): Gdk-WARNING **: gdkdrawable-win32.c:1591: BitBlt failed: The handle is invalid." to fill up the terminal window when the desktop is unlocked. This only happens when the user enters their password after the screensaver has kicked in. The number of such errors that appear depends on how many times the window was redrawn while the desktop was locked. =20 The errors themselves seem to be completely benign so is there any way to trap and handle such warnings within LablGtk, to prevent them getting written to the terminal? I have had a look through the documentation but have not found anything yet. Alternatively, is there any workaround known for this issue in LablGtk? =20 Thanks, =20 Matt =20 ------_=_NextPart_001_01C582E2.35F2BB52 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi there,

I have an application which uses Lablgtk2 = under Windows XP. I have run into a known bug in GTK (http://bugzil= la.gnome.org/show_bug.cgi?id=3D137796) which causes errors of the form: “(camlprog.exe:1116): Gdk-WARNING = **: gdkdrawable-win32.c:1591: BitBlt failed: The handle is invalid.” = to fill up the terminal window when the desktop is unlocked. This only happens = when the user enters their password after the screensaver has kicked in. The = number of such errors that appear depends on how many times the window was redrawn = while the desktop was locked.

The errors themselves seem to be completely = benign so is there any way to trap and handle such warnings within LablGtk, to = prevent them getting written to the terminal? I have had a look through the documentation but have not found anything yet. Alternatively, is there = any workaround known for this issue in LablGtk?

Thanks,

Matt

------_=_NextPart_001_01C582E2.35F2BB52--