This question about gdk_parse_color() and the XParseColor format is more
likely to get a sensible answer on the gtk-list. I have CCed it.
> in the documentation at
> http://www.gtkmm.org/docs/gtkmm-2.4/docs/reference/html/classGdk_1_1Color.html#a0
> about
> Gdk::Color::Color(const Glib::ustring& v
Yegor Derevenets wrote:
I try to compile GLib-2.5.6 under FreeBSD 5.3-Release.
I'm really stupid. After reading 'man ld' second time I found solution. :-)
./configure CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/bin"
--
Yegor Derevenets
___
gtk-lis
Can somebody file a bug to fix the gdk_color_parse() docs? we
stopped using XParseColor, and thus stopped supporting all the
weird XCMS specifiers several years ago.
GTK+ also interprets #fff and #ff as pure black, not almost
black, and doesn't try to emulate the XParseColor bug in that
area.
Hello,
I was just wondering whether
g_list_next(foo)
and
foo->next
are really the same or not. It seems to me that they are but
that the former construct is preferable for object-oriented-like reasons.
Thanks,
Neil
___
gtk-list mailing list
[EMAIL
I recently ported my application from V1.2 to V2.X of GTK. The one
item I haven't been able to figure out is how to force it to use a specific
font. Here is the code for V1.2 which worked fine:
gtk_rc_parse_string("style \"nm1\" { font =
\"-adobe-helvetica-medium-r-normal-*-12-*-*-*-*-*
