XYplorer Beta Club

Hi,

I've got a two-screen setup, and run 2 instances of XY (with different .ini files -- GREAT feature!) on my second screen, but each time I start up, each of the windows initially opens with the left edge (it appears to be 32 pixels) of the window on the first screen. The vertical position appears to be right, but horizonally it's shifted to the left but quite a bit...

Does anyone else have this problem, or is there something I can change to get them to start in the proper location?

Thanks!

andy

avsfan wrote:I've got a two-screen setup, and run 2 instances of XY (with different .ini files -- GREAT feature!) on my second screen, but each time I start up, each of the windows initially opens with the left edge (it appears to be 32 pixels) of the window on the first screen. The vertical position appears to be right, but horizonally it's shifted to the left but quite a bit...

Having only one screen it's hard to debug.

Is it like this?: when you just open and close repeatedly, the window moves about 32 pixels to the left each time? (You can verify the exact amount by looking at INI key WinX)

EDIT: I changed something. Check the next BETA...

admin wrote: Having only one screen it's hard to debug.

Is it like this?: when you just open and close repeatedly, the window moves about 32 pixels to the left each time? (You can verify the exact amount by looking at INI key WinX)

EDIT: I changed something. Check the next BETA...

I'm traveling, so I also only have one screen today! I'll check this when I return.

Actually, it always starts off with the left side being 32 pixels (I believe) to the left of the right-side screen edge. I'll check it and let you know for sure using the tip above for the WinX key).

Thanks for the reply!

andy

I somehow missed this thread earlier, otherwise I could have confirmed avsfan's bug...it did exist. But whatever you did in this last beta fixed the problem.

JustinF wrote:I somehow missed this thread earlier, otherwise I could have confirmed avsfan's bug...it did exist. But whatever you did in this last beta fixed the problem.

Confirmed -- this bug appears to be squashed!

Thanks, Don!

andy