intellahide's behavior when switching workspaces

Bug #592666 reported by Paul Tagliamonte
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docky
Fix Released
Low
Robert Dyer

Bug Description

Running 10.04 LTS

Docky dpkg version 2.0.2-1

Everything works great with the exception of intellahide's behavior when switching virtual desktops when using compiz ( and an animated switching between desktops ).

Docky sees that there is nothing covering where it wants to go when switching, and peeks its head out. When the animation is complete, docky figures out that it's being covered again, and pops back offscreen.

It leads to an annoying bounce behavior when switching desktops with animation ( but perfect without animation! )

One idea would be to make a longer timeout period between when it figures out it's free and when it actually pokes out.

Just an idea.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Steps to reproduce:

  * Enable desktop wall.
  * Open up application and place it against docky. Docky will disappear.
  * Switch to an adjacent workspace, and open up an application against docky.
  * Switch back and forth.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

This bug is invalid. It looks to only do this with VirtualBox in Seamless mode. My guess is this is not a docky issue. Marking invalid.

Changed in docky:
status: New → Invalid
Revision history for this message
Danielle Foré (danrabbit) wrote :

Not invalid. I can confirm on my machine. Using desktop wall and switching back and forth with intellihide. Interestingly, it doesn't affect window dodge.

Changed in docky:
status: Invalid → Confirmed
Robert Dyer (psybers)
Changed in docky:
importance: Undecided → Low
assignee: nobody → Jason Smith (jassmith)
Revision history for this message
Robert Dyer (psybers) wrote :

I can not confirm this (at least not with Desktop Cube).

Changed in docky:
status: Confirmed → Incomplete
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Let me paste my bug report again, FYI

Steps to reproduce:

  * Enable desktop wall.
  * Open up application and place it against docky. Docky will disappear.
  * Switch to an adjacent workspace, and open up an application against docky.
  * Switch back and forth.

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

Ok so it happens with Wall but not Cube.

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

By default the wall slide duration is 300ms.

Our code waits 200ms. I am reluctant to change this. I can make it gconf configurable though.

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

Fixed in rev 1548. To get the behavior you want, you will have to edit this key:

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

Default is 200ms. Since the default wall animation is 300ms, I would suggest setting this key to 350.

Changed in docky:
status: Incomplete → Fix Committed
assignee: Jason Smith (jassmith) → Robert Dyer (psybers)
milestone: none → 2.0.5
Revision history for this message
Paul Tagliamonte (paultag) wrote :

Thanks, Robert. I'll check this out in the morning when I'll be up for rolling a deb

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

Note that I could in fact query Compiz via dbus, get the animation time from them (which would also tell me if you are even using Wall) and then set it +50 in Docky's timeout. But that seems a bit overboard to hard code to 1 Compiz plugin.

Not to mention most people using the Wall plugin probably dont even notice this behavior. ;-)

I'll keep it in the back of my mind though.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Aye, I think depending on compiz libs would be an issue ( esp if the user does not use compiz -- can anyone say usless libs? ), but I do like the "automagic" aspect.

Perhaps a line in the docky settings menu that plays with gconf's setting?

Might be cool to add a simple ramping algorithm for intellahide too, set the threshold to 200 units, and have a coefficient for the behavior ( 1/8? )

On a detected double bounce apply 1/8(threshold) + threshold or something ( Thank you RTT algorithms! ) . Might still annoy some people, but people that anal tend to know how to use gconf ;)

Thanks again, Robert, that was a quick fix, I appreciate the time :)

Changed in docky:
milestone: 2.0.5 → 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.

Other bug subscribers

Remote bug watches

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