#1545 Open-Maximized Forgotten When Application Closed

[Gillum]

Bug 1530 fixed the problem that the "open maximized" feature/setting was forgotten when a database is unlocked.

I am finding that this "forgetting" occurs when the application and database are closed.

For example, every time I re-open a database after a reboot/login, the window opens with this "cover the screen but not actually maximized" (same behavior as was seen before on unlock).

[A M]

This became a bit entangled. So, in v3.45 I see the original wrong behaviour described in this bug. The previously maximized window is restored to cover the screen but not actually maximized.

Since v3.45 several changes went in to address similar problems (bugs 1517 and 1530) after unlock.

Now the recent v3.58 and v3.59 have a different wrong behaviour :-) The previously maximized window is restored to some small default size at position (0, 0).

I think I see the problem in DboxMain::OpenOnInit(). I will try to make this better.

[Rony Shapiro]

Fixed in commit 7de717751
Will be in next release.

[Gillum]

I am using 3.60 64-bit on Windows, and this problem persists.

[A M]

Hey @gillum, could you please share the exact sequence of step to reproduce what you see with 3.60? Possibly another issue.

[Gillum]

I will try to reproduce it. It happened to me again today (with two files), but when I try to get it to recur deterministically, it did not.

[Gillum]

I still get this frequently, but I cannot reproduce it deterministically.

I am wondering whether it is tied to some setting that I am using that is not common.

Perhaps the "Allow multiple instances" option? I keep that set. Is there a possibility that having the option may result in the app taking different paths on database closure and perhaps one of those paths loses the window-size setting?

[Gillum]

Could this have been fixed in 3.65.1?

GH1092 Size and position of main window is now restored correctly on displays with scale > 100%.

I run my Windows display scaled at 125%.