Add some type of delay or threshhold to expose docky.

Bug #502657 reported by digger vermont
34
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Docky
Fix Released
Wishlist
Robert Dyer

Bug Description

I commonly use a maximised window with my netbook (the screen resolution is 1024x600)

Without Docky I can quickly move the cursor all the way to the edge of the screen to use the vertical scrollbar.

When using Docky and a hidden panel, hitting the edge of the screen with the cursor causes the dock to be exposed. I then have to move back toward center screen to collapse the dock and then carefully appoach the scrollbar on the edge.

One thought is to require the cursor to be held in place on the edge for a moment before the dock is shown when the window is maximised.

Mostly Docky is coming along nice, thanks!

Revision history for this message
Robert Dyer (psybers) wrote :

We could probably add a gconf only config that lets you set a delay, defaulting to 0. This seems easy enough and shouldnt overly complicate the code. Thoughts, Jason/Chris?

Changed in docky:
assignee: nobody → Jason Smith (jassmith)
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Bernhard (b.a.koenig) wrote :

Another idea that I remember somebody had in #docky was to have a smaller "hotspot" for triggering docky. For example a smaller area in the lower right bottom of the screen.

Revision history for this message
Serrano Pereira (serrano-pereira) wrote :

I think many people will find this option useful, so I think an option for setting a delay in the Docky Configuration (instead of just gconf) would be handy.

Revision history for this message
Robert Dyer (psybers) wrote :

Another idea, from one of the duplicate bug reports:

The designers at the Gnome Usability Hackfest figured out that autohiding panels are a lot more useful when unhiding is velocity-sensitive. Basically the idea is that it's easy to tell when the user actually *wants* their panel, because they throw their mouse at the bottom of the screen. If their mouse just happens to touch the bottom of the screen while they are working, it does not unhide. This would even better for Docky, as users tend to auto-hide their docks much more than their panels.

See these links for details:
http://www.gnome.org/~seth/zuhanden-gnome3.pdf (PDF, page 5)
http://blogs.gnome.org/seth/2010/02/26/let-the-wild-rumpus-begin/
http://arstechnica.com/open-source/news/2010/02/task-pooper-could-revolutionize-gnome-desktop.ars

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

I'd be happy with a simple gconf entry where I could define a delay. I love using Docky (great job, thanks to all developers), the only minor thing is dislike is the immediate pop up when touch the screen edge.

Revision history for this message
Robert Dyer (psybers) wrote :

Fixed in rev 1493.

Set this GConf key:

/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay

The value is the number of milliseconds (ex, 1000 == 1 second) to wait before unhiding. This is only used when unhiding with the mouse cursor. Make sure you restart Docky to see the new setting.

Changed in docky:
assignee: Jason Smith (jassmith) → Robert Dyer (psybers)
status: Confirmed → Fix Committed
Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

This is broken with zoom enabled. When your mouse is along the zoom edge, you see the tops of the zoomed icons. gtk-recordMyDesktop isn't working for me right now, so I couldn't make a video.

Steps to repeat:
1. Put a relatively high (~1 second) value in the gconf field.
2. Enable zoom.
3. Move your mouse along the docky screen edge.

Docky 2.1.0
bzr docky r1497 ppa

Revision history for this message
Robert Dyer (psybers) wrote :

@Matthew: please report this as a bug.

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :
Robert Dyer (psybers)
Changed in docky:
milestone: none → 2.1.0
Changed in docky:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.