Background glitch

Need Help

from WinCustomize Forums
I'm using the free version of ObjectDock and love it. However I'm experiencing a glitch with the backgrounds when a window touches it. The glitch is that the 'touched' portion of the background vanishes. This also happens if I right click on the Dock, the context menu causes whatever part of the Dock it overlaps to to vanish. All icons/docklets are still visible though. Even when I dock it to the left side, if it touches my taskbar that part of the background will vanish. I am running Windows XP SP2.

What is causing this and how do I fix it?

Thanks,

Paul.



objectdock
2,574 views 8 replies
Reply #1 from WinCustomize Forums Top
got a screenshot?

I'm running the free... top, right, bottom, left... I'm not seeing any disappearance.

what graphics/drivers?

Reply #2 from WinCustomize Forums Top
How do I post a screenshot? When I click insert image it asks for a url. I have the screenshot saved to my harddrive. Where can I upload the image?

I have an ATI Mobility Radeon 9000 in a Toshiba a70 laptop.
ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from WinCustomize Forums Top
Upload it somewhere like imageshack.us, then insert it.
Reply #4 from WinCustomize Forums Top
Ok, for some reason I'm not having this problem today but I've had it over the last few days. Here's a couple of screenshots because I know this will no doubt raise its ugly head again.



Reply #5 from WinCustomize Forums Top
What dock is that your using? The top shot looks like somethings wrong with the background itself...could be wrong but can't tell till I can see the background.ini file. Is it doing this with any background or just some?
Reply #6 from WinCustomize Forums Top
ObjectDock background = Aero Zoomer #3. If you are referring to what is in my taskbar, that's FreeLaunch. This glitch occurred with any background. Took a bit of searching but I found the background.ini in non-tabbed\aero no 3 (no tabs) folder.

Now as I mentioned earlier I'm not experiencing the problem anymore but as a heads up if it happens again, what should I be looking for?

Here are the contents of the background.ini:

[Info]
Name = Aero Zoomer #3
ColorMe = 0
TextColor = 0 0 0
ShadowColor = 255 255 255

[BackgroundTop]
Image = BackgroundTop.png
LeftWidth = 43
TopHeight = 34
RightWidth = 43
BottomHeight = 14
ContentBufferLeft = 6
ContentBufferRight = 6
ContentBufferTop = 14
ContentBufferBottom = 1
OutsideBorderTop = 16
OutsideBorderLeft = 16
OutsideBorderRight = 16
OutsideBorderBottom = 40

[BackgroundBottom]
Image = BackgroundBottom.png
LeftWidth = 43
TopHeight = 22
RightWidth = 43
BottomHeight = 26
ContentBufferLeft = 6
ContentBufferRight = 6
ContentBufferTop = 1
ContentBufferBottom = 14
OutsideBorderTop = 40
OutsideBorderLeft = 16
OutsideBorderRight = 16
OutsideBorderBottom = 16

[BackgroundLeft]
Image = BackgroundLeft.png
LeftWidth = 34
TopHeight = 43
RightWidth = 14
BottomHeight = 43
ContentBufferLeft = 14
ContentBufferRight = 1
ContentBufferTop = 6
ContentBufferBottom = 6
OutsideBorderTop = 16
OutsideBorderLeft = 16
OutsideBorderRight = 40
OutsideBorderBottom = 16

[BackgroundRight]
Image = BackgroundRight.png
LeftWidth = 22
TopHeight = 43
RightWidth = 26
BottomHeight = 43
ContentBufferLeft = 1
ContentBufferRight = 14
ContentBufferTop = 6
ContentBufferBottom = 6
OutsideBorderTop = 16
OutsideBorderLeft = 40
OutsideBorderRight = 16
OutsideBorderBottom = 16

Reply #7 from WinCustomize Forums Top
Well...as long as the Left/Rightwidth and Top/Bottomheight of the actual image being used as the background isn't bigger than the image itself it shouldn't cause that to happen. Other than that this is the first time I've ever seen that happen.

You could try writing the developer [email protected] and ask him about it...he might have a better idea about it.
Reply #8 from WinCustomize Forums Top

Well...as long as the Left/Rightwidth and Top/Bottomheight of the actual image being used as the background isn't bigger than the image itself it shouldn't cause that to happen. Other than that this is the first time I've ever seen that happen.

You could try writing the developer [email protected] and ask him about it...he might have a better idea about it.


Ok, thanks and so far so good, it's still working fine.