Emulator Issues #2940
closed
Dolphin window can appear at very high negative positions
0%
Description
What steps will reproduce the problem?
1.Don't know excatly, i think it's somtimes after crashes or changing desktop resolution...
2.When starting up dolphin, it's Window will appear at a negative position like (x= -32000; y= -32000) and is out of cursor-reach.
To fix it you always have to open "Dolphin.ini" and set "MainWindowPosX" and "MainWindowPosY" to positive values.
What is the expected output? What do you see instead?
I expect the dolphin window to always show up on it's latest position.
Dolphin version with the problem? Other Dolphin version without the
problem?
32-bit or 64-bit and any other build parameters?
r5919 64-bit
OS version and versions of tools/libraries used?
Windows 7
Please provide any additional information below.
I would recomend to check the two values from the "Dolphin.ini" on exe-startup and correct them to fit in the current desktop resolution. Then set the position of the Dolphin-window again.
Updated by CuentaSpam23 almost 14 years ago
This is a really simple patch, If any of the values is negative then we will change them to 0.
This is not a real fix but It works for me
Updated by BhaaL over 13 years ago
- Status changed from New to Questionable
Can you reproduce this (without your patch)? r4928 supposedly fixed this when closing Dolphin while being minimized. Other than that, it should not appear at -32000
Updated by pascal.jouy over 13 years ago
+1.
For me, it is the rendering window which is at -32000.
Maybe the problem is with the rendering window only, may it be in Dolphin's main window or on a separate window.
Updated by BhaaL over 13 years ago
Would you mind telling us the GFX Plugins used?
Updated by
Updated by BhaaL over 13 years ago
Could someone please try this patch?
http://pastie.org/1227381
It's based on ayuanx's fix back then and follows the idea of Cuenta's patch, except that it does allow certain negative values (whenever the secondary monitor is at the left side of the primary monitor)
In case it doesn't help, the other thing to test would be droid's fix in r4928 which may not trigger OnMove/OnResize and store the wrong stuff anyways (or we're missing another event but OnClose that shows the same/similar behavior).
Updated by BhaaL over 13 years ago
- Status changed from Work started to Fixed
This issue was closed by revision r6286.