objectdock forgets position when switching resolutions

I play Counter-Strike in a lower resolution than my desktop and when I exit the game, ObjectDock is no longer at the bottom; it thinks Im still at the lower resolution.

Any ideas? I hate to have to continually reset its position after playing CS:S.
5,868 views 12 replies
Reply #1 Top
Any ideas? I hate to have to continually reset its position after playing CS:S.


Play counter strike in the same resolution.
Reply #2 Top
This is the same for DX when i play WoW. Things just don't go back to where they should be.
Play counter strike in the same resolution.


Games just don't support all resolutions. I really should not have to change the resolution that i like to use.
Reply #3 Top
ObjectDock still seems to have many problems with screen changes, and I suspect they are all related. In my dual monitor config, whenever I log off and then back on, my tabbed docks are always on the wrong monitor now.

for example, what should be...

MONITOR A (primary, on the left)
tabbed system tray dock, right side, attached to edge/autohiding
tabbed dock (folders), bottom, attached to edge/autohiding

MONITOR B (secondary, on the right)
taskbar zoomer, left, centered
tabbed autohiding dock (links), top
normal zoomer (applications), bottom, centered

...keeps coming back as...

MONITOR A (primary, on the left)

(nothing)

MONITOR B (secondary, on the right)
tabbed system tray dock, right side, attached to edge/autohiding
tabbed dock (folders), bottom, attached to edge/autohiding
taskbar zoomer, left, centered
tabbed autohiding dock (links), top
normal zoomer (applications), bottom, centered

...so I have to manually drag the tabbed docks back from the secondary to the primary monitor and then re-enable attach to edge to return those docks to their proper position/functionality.

This is currently happening on Vista 32, but it always happened on XP as well, so I suspect this is a long-standing behavior problem with ObjectDock, as I can't remember a time when it wasn't broken this way.

I hope this helps troubleshoot the problem.
Reply #4 Top
I haven't had problems with my dual monitor setup.
Primary on left, secondary on right.
I have a zoomer taskbar on my primary (magnification) right, centered, keep on top
I have a zoomer systray on the secondary (no effect) bottom, right, keep on top
A tabbed dock on the secondary (zoom effect) attached to the edge, show as drawer, top, center.

Running XP Pro SP2 on a domain.

This may be key.....both screens run at the same res 1600x1200. Seems to me I had some issues back when I was using a laptop with a secondary with the laptop at 1920x1200 and the secondary at 1280x1024 but it's been over a year so I can't remember for sure.
Reply #5 Top
Lantec,

Thanks for offering points of comparison. Here are the key differences as I see them.

On the machine showing this problem my primary is 1680x1050 and my secondary is 1920x1200. So yes, they are different resolutions.

You don't have any tabbed docks on your primary. Tabbed docks on the primary are the only ones that migrate to the secondary monitor for me. The tabbed dock on my secondary always remembers where it is and what monitor it is supposed to be on.

For me, zoomers always remember the monitors correctly (probably because they have a "hard wired" monitor display setting).

Hope this helps narrow things down.

:}

PS My emoticons in the above post are supposed to be sad ones, not angry ones.
Reply #6 Top
I don't actually chance resolution (1280 x 1024) when playing MVP Baseball 2005, but when I exit it the tabbed folders that are normally in the top right corner are closer to the middle of the top edge and I have to shift them manually. Is there really no way to lock the position?
Reply #7 Top
I think all the program needs to do is save the monitor # (already in the code for zoomers) and store the position as pixel offsets or as percentages in X/Y. My guess is this an an old code snippet than didn't get updated when zoomers added multimonitor support. Then again, I could just be talkin' out of my arse.
Reply #8 Top
Ooops, I forgot about another dock. I have a non-magnifying, fixed position zoomer (with clock, cpu, etc.) on Display 1. It doesn't autohide and it's position is never lost, so it always shows up on Display 1 (Primary, Left) even though the two autohiding tabbed docks keep appearing on Display 2 at logon.
Reply #9 Top
Did some logging on/off with different settings tonight (just finished a delivery, so I was bored), and it appears I've narrowed the problem at my end down to the "Attach to Edge" option for Tabbed Docks (how they "autohide").

If that option is off, the tabbed docks remember their positions between shutdowns/restarts/logoffs. If that option is on, then the tabbed docks appear on the wrong monitor.

So it appears as though Attach to Edge gives Tabbed Docks in ObjectDock a headache under multiple monitors (as described above).

Can someone at Stardock forward/refer this thread to the proper person? Thanks.
Reply #10 Top
Another clue...

I checked the changelist and found this note "x-Fixed problem where tabbed docks could appear when mouse was on on the opposite side of the screen from where they are."

So I tried logging on/off and placing the mouse in different places. Sure enough, if I leave the mouse on my primary monitor when I start ObjectDock up, the tabbed docks on my primary monitor show up on my primary monitor like they are supposed to. If I have the mouse on one of my other three screens (two on this one, the other two vs. multiplicity pro) the tabbed docks show up on my secondary monitor.

So whatever bug was supposedly fixed in this latest beta apparently wasn't actually fixed all the way.
Reply #11 Top
I just wanted you to know that I forwarded this to the developers. Thank you for the testing. I too was able to replicate the issue you were having under the parameters you listed.

Reply #12 Top
Hallelujah, brother Seabass. Thanks for going through the effort of reading my posts and then confirming this very strange bug. I'm sure the programmer(s) will be able to suss this out now. Again, thank you.