PiP messing region0 position while swapping

[Oldin]

Hi again.

Not sure if this is a bug or just something you hadn't thought about. I have 5 windows set up one on my right side 19" monitor and 4 on my left side 22" monitor. The aspect ratios are the same on both monitors. region0 is the main one that is on the display2 in the maximizer setup and region1-4 are on the display1. If I always switch back and forth between the main window and a different window things go smoothly. This is a bit hard to explain so I'll try to do it in steps

- Situation normal
3 2
4 1 0


-swap one

3 2
4 0 1

at this point if I swap back to one either by pressing one or zero everything works as it should. If I swap to 2 for instance the situation will look like

32 0
4 1

The maximizer loses proper positioning for region 0 and swaps it over to display1 in the top left corner. Granted it is at the top left corner on display2 too.

The same happens if I press the hotkey for region 0 first and then before pressing region 0 hotkey again press another hotkey.
There doesn't seem to be any way to rectify the situation short of shutting down the clients and restarting with the keyclone command again.

[keyclone]

i'm not exactly sure what you mean... but i do have on the list a couple of items to address changing the maximizer on the fly.

for now, can you go into setup and adjust the maximizer and hit apply ... does your screen jump back to normal?

[Oldin]

Hey, that was easy to fix it on the go...



and that is what the screen looks like when it is affected. The wow on the right screen is not reacting to anything and is basically just an image of the screen. By dragging a window over it I can get the desktop to show there again. Basically the right screen just stops updating until there is something ot update. That Katso myös on the right screen is normal windowsxp window suggestions box that has updated after the pip failure.



Is what it normally looks like. If any other than the right hand window is focused nothing strange happens and pip works perfectly. If the main window is active And that window is being moved from one area to the other in the other screen I the big window ports to the other screen.

to clarify actually all I need to do to solve the issue is to open the setup and hit ok.

[keyclone]

hmmm.. i have had that situation when i overload my machine. do you think you might be getting close to max memory when this happens? (max memory == starting to swap to disk more.. hitting the page file)

a side note: why not make the main full screen and adjust the clones so they are vertical centered but still the same aspect ratio? it might look nicer on your main.

and depending on your play style, if you find you don't go to your clones very often, how about shrinking them a bit, taking up less room, and just pip swapping when you need them? the smaller size would radically drop the pixels/sec pushed from them to the graphics card.. .leaving more for your main and pip-swap

[Oldin]

Main is full screen. That black is there because of the differing sizes of the monitors. Right now trying to drastically reduce the size of the secondary character's screens. Still happens every time the main wow changes from one small window to another small window. If wow that starts on big screen is going to small or small to big then nothing interesting happens. RAM usage while playing is pretty strictly at 60% or I haven't noticed any major spikes there.