Re: Those durn open API bugs

[Havoc Pennington <hp redhat com>]

Tim Janik <timj gtk org> writes: 
> > Misc GTK+
> > =========
> > 53151  gtk_window_set_size(), gtk_window_set_location()
> >   Notes:    API agreed upon now, patch exists
> >   Puntable: No
> >   Breakage: Some functions will be deprecated
> >   Time:     ?
> 
> i think this one needs updating, we applied havoc's changes that resulted
> from a prior irc meeting where we had consensus. or is there another patch
> pending against current CVS that i missed?

I already closed this bug, Owen just accidentally left it in the mail.
 
> > 59032 activatable cell renderers API [*]
> >   Notes:    
> >   Puntable:
> >   Breakage:   
> >   Time:    
> 
> is this the ::can_activate vs. ::activatable issue i brought up?

That and also the current way that "activatable" works is pretty lame
(if a renderer is activatable, certain GdkEvents are let through to
it).

I know we had some other way to implement this, probably an activate()
method on the renderer, but I'm not sure I remember. The events thing
forces a renderer to be activatable in order to get all the events.

In general the whole events-to-renderer thing is broken:

  http://bugzilla.gnome.org/show_bug.cgi?id=50344
 
it only forwards button press events.

> > 59173 GtkTreeView code should use GtkSortType instead of GtkTreeSortOrder [*]
> >   Notes:    
> >   Puntable:
> >   Breakage:   
> >   Time:    
> 
> what about the GtkTreeSelectionMode vs. GtkSelectionMode issue i
> also brought up?

Hmm, closed.  http://bugzilla.gnome.org/show_bug.cgi?id=59034
Granted, it was not closed with adequate explanation. ;-)

IIRC we decided GtkSelectionMode is broken because there are only two
proper selection modes, one that allows 0/1 items to be selected, and
one that allows many items to be selected. This is how other platforms
work. It's too confusing to users otherwise.

ergo:

typedef enum
{
  GTK_TREE_SELECTION_SINGLE,
  GTK_TREE_SELECTION_MULTI
} GtkTreeSelectionMode;

However, it might be nicer if MULTI was not abbreviated, and it might
be nicer if this new enum was not tree-specific.

I only heard the discussion of this while I was doing something else,
owen and jrb were the ones who figured it out, so they can probably
explain better.

Havoc