After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 451202 - New tooltips API has too long default timeout
New tooltips API has too long default timeout
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.11.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-06-26 10:25 UTC by Richard Hult
Modified: 2011-02-04 16:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch (411 bytes, patch)
2007-08-27 14:24 UTC, Alexander “weej” Jones 		none Details | Review

Description Richard Hult 2007-06-26 10:25:00 UTC 
The new tooltips API uses a 1500 ms delay before showing a tooltip. The old uses 500 IIRC, it would make sense to use the same in the new one.
Comment 1 Pedro Villavicencio 2007-08-22 15:22:03 UTC 
there's also an Ubuntu bug about it: https://bugs.launchpad.net/gtk/+bug/133919
Comment 2 Alexander “weej” Jones 2007-08-27 14:24:00 UTC 
Created attachment 94430 [details] [review]
Patch

Set the default GtkSetting to 500 instead of 1500. Thanks to Ben Berg for the pointer.
Comment 3 Kristian Rietveld 2007-08-29 09:17:10 UTC 
I originally went with 1500 here because it was suggested (together with the browse mode) in one of the tooltips API discussion threads a year ago or so.  I have no problems with changing it to 500, though we might want to tweak the browse-mode-timeout.


Tim, any opinions on this?
Comment 4 Tim Janik 2007-08-29 10:07:19 UTC 
(In reply to comment #3)
> I originally went with 1500 here because it was suggested (together with the
> browse mode) in one of the tooltips API discussion threads a year ago or so.  I
> have no problems with changing it to 500, though we might want to tweak the
> browse-mode-timeout.

> Tim, any opinions on this?

i agree that 500ms is a good default timeout. the browse mode timeout should be below 100ms at least though, to provide some kind of "fluent" feeling. around 60ms may be good.
Comment 5 Kristian Rietveld 2007-08-29 12:03:51 UTC 
Committed 500,60 on trunk (r18701).