Bug (?) In latest version of Objectdock (Free)

from WinCustomize Forums
I was wondering if anyone else has had a problem with a setting in Objectdock. I have set my dock to always stay at the bottom and I have it positioned at the top of the screen. When I minimise a window it launches the icon at the end of my dock, even though the setting to keep it to the bottom is definately active. I had no trouble with this on previous versions. The new version was installed straight over the old if this is any help (other new features work fine).

Any help would be appreciated as I was looking forward to purchasing plus version, but i will wait if this is definately a bug and not me being a plonkler.
wincustomize
1,942 views 4 replies
Reply #1 from WinCustomize Forums Top
"What does stay at the bottom" and "it launches icon at the end of my dock" have to do with one another?
Reply #2 from WinCustomize Forums Top
I think he means the click on the minimize titlebar button is passing through and activating the Dock icon underneath.
Object Desktop - Get all of our enhancement utilities in one suite
Reply #3 from WinCustomize Forums Top
If pictoratus is right and that's what he means, then yes, it is a known bug...



Powered by SkinBrowser!
Reply #4 from WinCustomize Forums Top
Pictoratus is correct, it is indeed going through all my windows that are on top of Objectdock and activating the icon underneath (which is set to always stay at bottom). This is obviously a major pain in the arse when using maximised windows. To add further confusion there has been the odd occasion when it doesn't do this. It will always activate an icon through all windows when I first run Objectdock. Then if i fiddle with the settings - ie change it to a different method, ok it, and then change it back to "always on the bottom" this seems to make it work for a while. But it is strange and temperamental. Hope this helps. If it is a bug I am very dissappointed and hope the Stardock guys can sort it out soon, so I can make my purchase of the Plus version, which I am assuming carries the same bug.