Re: Tooltips patch [take 1]

[Damon Chaplin <damon karuna eclipse co uk>]

On Sun, 2007-03-18 at 01:22 +0100, Tim Janik wrote:

> the main reason for ::has-tooltip is efficiency, because the new tooltips
> potentially do many tip checks currently (ca. on every mouse motion, however
> we might implement some coalescing to limit the number of tip checks to
> 16-25 per second), and for each such tooltip check, multiple widgets maybe
> queried (the innermost child widget and all its parents worst case).

"has-tooltip" is a bit kludgy though. It would be better if it wasn't
needed. (It will probably confuse people using GUI builders. Or GUI
builders will have to add special code to avoid showing it.)

Do we need to emit "tooltip-query" in the motion event? Why can't we
just setup/update the timeout handler in the motion event and only emit
"tooltip-query" when the timeout fires? That sounds more efficient
anyway.

If we do that, and tell people who use "tooltip-query" that they must
set the event mask to get motion events, then we may not need
"has-tooltip".

Damon