[Please CC replies to [EMAIL PROTECTED]
Hi,
I'd like to create a pixbuf sub-column inside a GtkTreeView column that
doesn't take up any space when the pixbuf is empty. Currently I'm setting
up the view like this:
column = gtk_tree_view_column_new ();
renderer = gtk_cell_renderer_pixbuf_n
[Please CC replies to [EMAIL PROTECTED]
Hi,
I'd like to create a pixbuf sub-column inside a GtkTreeView column that doesn't
take up any space when the pixbuf is empty. Currently I'm setting up the view
like this:
column = gtk_tree_view_column_new ();
renderer = gtk_cell_renderer_pixbuf_n
On Wed, 12 Feb 2003, Florin Iucha wrote:
> Yes, "strip" helped. I was expecting the "make install" to already
> strip the libraries.
we have 'make install-strip' for that
--
.--= ULLA! =-. `We are not here to give users what
\ http://cactus.rulez.org \ they
On 28 Aug 2002, Murray Cumming wrote:
> That might be neat if NULL always means "use default cursor", but I only know
> about that one gdk_window_set_cursor() function.
Gnome::Canvas::Item::grab() is the other one I can think of.
--
.--= ULLA! =-. `We are not here to
On 28 Aug 2002, Murray Cumming wrote:
> I suppose we could create the abstract concept of a default cursor
> (implemented as a boolean) and check for it in each method that takes a
> cursor. Is that what you mean?
well, by 'default cursor' I mean anything that's gobj() method returns
0... that k
On 28 Aug 2002, Murray Cumming wrote:
> > I hope you don't mean you wrote a set_cursor override.
>
> I meant "overload". I must stop doing that.
Actually, I meant overload as well
> > That won't work in
> > other cases, like Gnome::Canvas::Item::grab.
>
> I don't understand. It's just meant t
On 28 Aug 2002, Murray Cumming wrote:
> > Thanks, you 've proved that GTK itself works fine :).
> > I just was wondering if GTKMM has simple way to do this, also.
> > For example, someone could provide a patch with another override for
> > set_cursor() in Gdk::Window:
>
> I did this recently in
[please CC replies to [EMAIL PROTECTED], thanks]
Since GTK+ 2.0 has been released for more than a month, I decided to get
up-to-date with GTKmm and other related packages to fix Gnomoku which has
surely bit-rotten in the last months. Back when I first ported it to GTK+
1.3, it was very slow, but
