RE: Gtk::Grid::attach_next_to

[Thomas Harty <t harty1 physics ox ac uk>]

Okay, that's what I'd assumed.

Bug filed at https://bugzilla.gnome.org/show_bug.cgi?id=739340.

Related: what's the best way to get the number of rows/columns currently in a Gtk::Grid?

Tom

________________________________________
From: gtkmm-list [gtkmm-list-bounces gnome org] on behalf of Chris Vine [chris cvine freeserve co uk]
Sent: 26 October 2014 10:15
To: gtkmm-list gnome org
Subject: Re: Gtk::Grid::attach_next_to

On Sat, 25 Oct 2014 11:43:17 +0000
Thomas Harty <t harty1 physics ox ac uk> wrote:
> The documentation for Gtk::Grid::attach_next_to
> (https://developer.gnome.org/gtkmm/stable/classGtk_1_1Grid.html#ae42f1ae2fc23e16880c51438afa8fbcf)
> says that the sibling widget can be set to 0 to place the child
> widget at the beginning/end of the grid. Does this imply a conversion
> between int and Gtk::Widget&, or am I missing something?

This looks like an artefact from the documentation for GTK+ which has
been pulled in.   You cannot have null references in C++ so you will
probably have to use the C interface to get this to work (that is, call
gtk_grid_attach_next_to()).  For that purpose, you can call the grid's
and widget's gobj() method to get the pointers for the first and second
arguments for that function. Alternatively, if you want to stick with
the C++ interface, you could do the necessary calculations yourself and
call the attach() method.

You could regard this as a wrapper error, and file a bug.  However,
there is probably little that can be done about it, except provide a
new overload without the sibling argument.

Chris
_______________________________________________
gtkmm-list mailing list
gtkmm-list gnome org
https://mail.gnome.org/mailman/listinfo/gtkmm-list