Hallo.
After experimenting, reading GTK+ source code and documentation, the X
protocol and server specification, I think, that the current design of
motion feedback using motion hints is broken, and its X11 back-end is
broken for sure.
All GTK+ callback implementations you can find are broken
On 07/07/2009 10:29 AM, Davyd Madeley wrote:
On Tue, 2009-07-07 at 13:25 +0100, Behdad Esfahbod wrote:
Generally agreed. Makes the code so much simpler...
How do we avoid breaking API/ABI though?
Donno. I'm not the most qualified person to talk about GTK+ widgets anyway.
behdad
One
Hi,
I have a win32 glib multi-threads application (compiled by mingw, glib
only, no gtk+).
When I have two threads ... the application running OK. But when I add an extra
threads my application can still run, but has random error message:
gmem.c 175 failed to allocated 175 bytes ...
The
On Jul 13, 2009, at 12:57 AM, Thomas Wood wrote:
On Thu, 2009-06-18 at 22:45 +0100, Chris Wilson wrote:
On Thu, 2009-06-18 at 22:35 +0100, Thomas Wood wrote:
Thanks Chris. Obviously once the API is converted to pass in cairo
contexts, the context creation/destruction will happen outside of
