Moneymanagerex: Always Opens on Wrong Monitor

[mrando820]

MMEX version:

• [X] 1.3.6

Operating System:
Windows X

Refuses to remember which monitor to open on.

I move the program to my secondary monitor, but when I close it and reopen, it always opens on my primary. I checked the Settings database (sorry, forgot the name) and it's got the correct negative X,Y coordinates, but it still won't open on the secondary. I don't recall this ever happening on prior versions.

Reproduction

Is the bug reproducible?

• [X] Always

Reproduction steps:
Just open it, will always be primary monitor.

Expected result:
Open where it was when closed.
Actual result:
Opens with same dimensions as closed, but always on primary monitor.

Additional information

Tried deleting the configuration database, which recreates fine, and stores the coordinates, but it still opens on wrong monitor.

[vomikan]

I tried to reproduce it, but it didn't work. You can make the coordinates passed by parameters. But this is for geeks.

[mrando820]

Thanks, going to try a complete uninstall/reinstall. I can’t imagine the code to open on a monitor has changed in years, so maybe something is corrupt on my end.

From: Nikolay [mailto:[email protected]]
Sent: Sunday, January 24, 2021 10:39 AM
To: moneymanagerex/moneymanagerex [e-mail]
Cc: mrando820 [e-mail]; Author [e-mail]
Subject: Re: [moneymanagerex/moneymanagerex] Always Opens on Wrong Monitor (#2826)

I tried to reproduce it, but it didn't work. You can make the coordinates passed by parameters. But this is for geeks.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/moneymanagerex/moneymanagerex/issues/2826#issuecomment-766410097 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ASSTCOTMN4G2OAMJR3Z3BMLS3RSNLANCNFSM4WQXK2VQ .

[mrando820]

Looks to me like the change for bugfix #214 caused this:
valx will be a negative number when the primary monitor is on the right, and the program was closed on the left monitor. That's fine, it shouldn't get assigned to zero. Or at least, so I believe. (mmex.cpp).

//BUGFIX: #214 MMEX Window is "off screen"
if (valx < 0)
    valx = 0;
else if (valx >= sys_screen_x)
    valx = sys_screen_x - valw;

if (valy < 0)
    valy = 0;
else if (valy >= sys_screen_y)
    valy = sys_screen_y - valh;

[vomikan]

2694