On Thu, 31 Jan 2008, Tor Lillqvist wrote:
> > In particular, the "loaders" directory is now gone due to Tor's
> > decision to build a monolithic gdkpixbuf library for GTK on
> > Windows, with all the loaders pre-embedded. Personally, I wish
> > he'd reconsider that.
>
> OK, you are the secon
I feel the same way. I can't think of an example off of the top of my
head, but I swear there have been things that the only way I figured
them out was by reading the python documentation and sort of guessing at
the C API. Yes I look at the reference docs on gtk.org and gnome.org.
> Date: Wed, 3
I looked the gimp install directory and I found this files :
- bin/*.dll
- etc/gtk-2.0/gdk-pixbuf.loaders
- etc/gtk-2.0/gtk.immodules
- etc/gtk-2.0/gtkrc
- etc/pango/pango.aliases
- etc/pango/pango.modules
- lib/gtk-2.0/2.10.0/engines/*
- lib/gtk-2.0/2.10.0/immodules/*
- lib/gtk-2.0/2.10.
On Jan 29, 2008 5:35 AM, Bin Chen <[EMAIL PROTECTED]> wrote:
[...]
>
> I can't see any code to transfer modified "display" structure to the
> server, this API is invoked by a XIM server so obviously the register
> stuff need to be accessed by other process, is there any shared memory
> trick in li
amol wrote:
> Hi,
> When we do gtk_buildable_set/get_name for any object created through
> GtkBuilder, GtkBuildable does g_object_set/get_data to return the
> corresponding name of object if its set/get_name are not overridden.
> But GtkWidget overrides set/get_name of buildable interface and doe
> > I would recommend *not* installing packages from other sources in your
> > MinGW folder.
> I did not know. It is better to install them in the directory of Code:Blocks
> (my IDE)?
No, that would also be mixing stuff from separate sources. I would
install them in a totally separate folder.
--
> In particular, the "loaders" directory is now gone due to Tor's
> decision to build a monolithic gdkpixbuf library for GTK on
> Windows, with all the loaders pre-embedded. Personally, I wish
> he'd reconsider that.
OK, you are the second person to oppose this change (if I recall
correctly),
