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 347199 - default panel unhide delay too long (slow!)
default panel unhide delay too long (slow!)
Status: RESOLVED DUPLICATE of bug 585963
Product: gnome-panel
Classification: Other
Component: panel
git master
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 347201 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-11 08:43 UTC by Dimitrios
Modified: 2009-06-18 07:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Dimitrios 2006-07-11 08:43:14 UTC 
Please describe the problem:
The default unhide delay of the panel (when a panel is auto-hidden) is VERY long.

When moving the mouse ontop of the hidden panel, it takes too long for it to appear. Some people may think this is a feature, but its not. Overall, during the use of a computer the experience of the user is worsened.

This delay creates a "my computer is too slow" effect. The user just sits there for a few seconds waiting for the panel to open.

I believe the delay should either be completely removed or at least make it considerably shorter (faster).


Steps to reproduce:
1. Create an auto-hidden panel
2. Move mouse ontop of hidden area
3. Wait for panel to appear


Actual results:
Panel appears with a long delay

Expected results:
Panel to appear instantly or at least faster

Does this happen every time?
Always

Other information:
Comment 1 Fabio Bonelli 2006-07-11 10:53:49 UTC 
*** Bug 347201 has been marked as a duplicate of this bug. ***
Comment 2 Mateus 2009-01-22 02:12:05 UTC 
I agree wholeheartedly.

Related to [[http://bugzilla.gnome.org/show_bug.cgi?id=528818 | Bug 528818 ]].
Comment 3 Vincent Untz 2009-06-18 07:15:22 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 585963 ***