On Tue, 18 Feb 2003 20:45:23 +0800, James Henstridge <[EMAIL PROTECTED]> wrote:
> > I have had to use the
> >"cursor_changed" signal which emits two signal on the first click because
> >no row was initially selected.
>
> With the new tree widget, the selection is abstracted as a separate
> ob
On Tue, Feb 18, 2003 at 07:00:27PM -0500, Anthony Tekatch wrote:
> I cannot find any reference to that on the GtkTreeSelection documentation page?
>
> http://www.gnome.org/~james/pygtk-docs/class-gtktreeselection.html
>
> Where is that documented?
See the bottom of
http://developer.gnome.org
> > What TreeView signal can I use to replace "select_row"?
>
> Try the GtkTreeSelection "changed" signal.
I cannot find any reference to that on the GtkTreeSelection documentation page?
http://www.gnome.org/~james/pygtk-docs/class-gtktreeselection.html
Where is that documented?
--
Anthon
On Tue, Feb 18, 2003 at 07:18:38AM -0500, Anthony Tekatch wrote:
> GTK used to have a CList widget with a "select_row" signal that was sent
> when a row was click upon. GTK2 only has a TreeView "select_cursor_row"
> signal which I cannot get to do anything. I have had to use the
> "cursor_changed
Anthony Tekatch wrote:
GTK used to have a CList widget with a "select_row" signal that was sent
when a row was click upon. GTK2 only has a TreeView "select_cursor_row"
signal which I cannot get to do anything. I have had to use the
"cursor_changed" signal which emits two signal on the first click
GTK used to have a CList widget with a "select_row" signal that was sent
when a row was click upon. GTK2 only has a TreeView "select_cursor_row"
signal which I cannot get to do anything. I have had to use the
"cursor_changed" signal which emits two signal on the first click because
no row was init
