OB+ Flyout menu leaves "icon ghosts"

Won't disappear except by closing OB+ and then starting it again

I'm using a flyout menu in a non-tabbed dock (active applications' icons to the left, that separator, and then my flyout menu + a clock to the right). The menu contains all my common programs, roughly sorted into categories like Internet, Audio, Graphics, Games etc. Underneath these I have all those programs.

I noticed that sometimes (increasingly often), the flyout leaves "ghosts" of the icons in the first level (Internet, Audio etc - not the second level [which would contain Firefox, ICQ, Winamp etc - the actual programs]). The ghosts won't disappear of their own accord, and they're really in the way. If I accidently click on one, the focus shifts from my current application to the dock. I can even right-click it, upon doing which I get the standard right-click popup you get if you right-click the actual dock (not an entry, but the dock itself).

One way to replicate this is to add more than 7 items into the first level of the flyout. Since all the items can't "fit" into the first level, you get those left and right arrows to spin the menu. If you keep spinning, more and more icons will leave ghosts (and more often than not at the very top middle spot, the item right above the flyout icon). I made a screenshot of how it ends up; it's not very easy to explain it in words.

Link


Any easy way to get around this?

Help would be greatly appreciated.
3,256 views 5 replies
Reply #1 Top
I have never seen this one, and could not reproduce it on my machine.

If you have not tried this yet, save the theme, then unload ObjectDock > go to "C:\Documents and Settings\"user name"\Local Settings\Application Data\Stardock" folder (where "C" is the letter drive, and "user name" is the name on the account when you are logged in), and delete the "ObjectDock" folder there - this will clear the cache.

If you can't see the "Local Settings" folder, go to "Tools>Folder Options>View tab" and select "Show hidden files and folders", then click "Apply".

You can then reload ObjectDock, which should load the default theme, then you can use the "Configure Dock" to load your previously saved theme. I don't know if this will help, but it will remove any possible issue with the current cache. If the issue remains, then it is either a bug in the program, a problem with the way the theme was set up, or (in my opinion, which may be wrong) a possible video adapter issue.

Other ideas if the issue persists:

The screenshot seems to show a number of instances of Firefox open, so perhaps it is a video resource issue. I would load "system information" and try to replicate it to see if you are using up your physical memory installed which would force virtual memory to be used.

You might leave more information about the folders you created for your applications? Did you create them in the start menu, or in a directory? Or did you create some sort of custom menu through the "Flyout menu" dialog?

I am happy to see if I can reproduce it on my machine to see if I can identify the problem, will check back later.

Good luck.
Reply #2 Top
This problem was reported by a few, but is supposed to be fixed in the latest version, 1.11.518u
Reply #3 Top
i found this problem as well.
BTW, I DON'T have more than 7 icons at that level. there are only 4.
problems arise then.
Reply #4 Top
Okay, I uninstalled and installed the latest version using SDCentral (v1.11.518u Plus), and that seems to have fixed it. Yay!

Corky_0> First of all, I created the fly-out menu by right-clicking the dock itself and navigating to Add -> New Fly-out Menu. Then I defined the contents by right-clicking the menu icon and choosing Dock Entry Properties (which opened the usual window from within which I added all my first and second level entries). It took a little while to get everything in there. ; )

As for Firefox instances and physical memory - I'm on a 1gb RAM system, and I'm running a little app called FreeRAM which shows the available amount of RAM in a little tray icon. I check it often to see it's not too low (which would be an indicator of some of my running applications malfunctioning and leaking memory), so at the time of the screenshot I'd wager I had more than 400mb RAM available.

I don't have a similar easy way to keep track of video memory, though. I'm using an ATi Radeon 9800Pro card (128mb), so while I don't think the video memory would fill up very easily, nothing's saying it wasn't full.

Well, since it seems to be working in this latest beta, I'm pretty content. =P