On 6/22/07, Matthias Clasen <[EMAIL PROTECTED]> wrote:
> On 6/22/07, Sven Neumann <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote:
> >
> > > so far, my take on the issue is that PyGtk should adapt to that
> > > change by not using tooltips->tips_data_li
On Mon, 25 Jun 2007, Kristian Rietveld wrote:
> On Mon, Jun 25, 2007 at 09:34:56PM +0100, Damon Chaplin wrote:
>> Tim said we get motion hints everywhere now anyway (though I can't see
>> where that is done in the code). See the last paragraph here:
>> http://mail.gnome.org/archives/gtk-devel-li
On Mon, Jun 25, 2007 at 09:34:56PM +0100, Damon Chaplin wrote:
> Tim said we get motion hints everywhere now anyway (though I can't see
> where that is done in the code). See the last paragraph here:
> http://mail.gnome.org/archives/gtk-devel-list/2007-March/msg00230.html
I don't think Tim was t
On Mon, 2007-06-25 at 15:38 +0200, Kristian Rietveld wrote:
> On Sat, Jun 16, 2007 at 12:18:34AM +0100, Damon Chaplin wrote:
> > Is "has-tooltip" needed for anything besides the efficiency issue? (e.g.
> > a11y or something?)
>
> In order for the tooltips implementation to work, we need to monitor
On Sat, Jun 16, 2007 at 12:18:34AM +0100, Damon Chaplin wrote:
> Is "has-tooltip" needed for anything besides the efficiency issue? (e.g.
> a11y or something?)
In order for the tooltips implementation to work, we need to monitor
motion and related events on the widget's windows. When has-tooltip
