Comment 9 for bug 688442

Ok, I finally got a fix committed for this bug. DockbarX now checks which monitor it's on when every time it needs that info instead of just checking once when DockbarX is starting/reloading. Hopefully that will do the trick. I also hope this fix doesn't slow down anything. I don't think that checking for monitor number for a window should use that many CPU cycles, but who knows?

I also noticed that VirtualBox 4.0.8 (perhaps older versions as well?) allows me to simulate dual screen so I will probably be better at fixing dualscreen bugs in the feature.