For a while now I have the issue that most of the time, comics seem to open wherever they want, with whatever size they want. It defaults to the configured windows usage (width/height etc), but the position on the screen is varying. Then I spend some time pulling the window to where I want it, resizing it so the frame elements are usable (often they are off screen), resetting the zoom so I can read, only to find everytime I open a new comic, it seems to default to wherever the hell it likes to be.
When I check "window x", "window y" in the configuration file, they change after every closing without me doing anything. When I open and close the same comic again and again, without touching anything, the values seem to rise up to a point, then hopping back. The comic seems to be wandering from top left to bottom right, so to say. Maybe it is trying some stacking smartguessing, but when I open only one comic, that's not what I want. I'd expect MComix to either remember settings per comic, or stay, windows-wise, wherever I closed it last time. That would be a relief. It's a fine reader, I like it, but that behavior is quite disruptive to the experience, I have to say. I can't quite tell you, when it was introduced, alas, but it's not for too long. Sorry for the vague info, but it took me some time to find a reproduceable behavior in that seemingly chaotic pattern of movements.
Oh, Version is 2.1.0, OS is Windows 10 64bit. Forgot to mention.
I believe this might have already been fixed recently. Please give the new version 2.1.1 a spin.
Ah, thanks for the info, that one came out three days after my post, it seems. Yes, it is a lot better. It seems to remember window width and jumps less. But it still jumps. Here are the values out of the preferences.conf (click arrow) after consecutive opening and closing the same file, without doing anything else:
preferences.conf
The pattern is recognizable, I think. The first two values are by my manual positioning, everything thereafter is the positioning pattern I'm experiencing. I get different jump sequences. But essentially the x position is always one of the multiples of 52, the y is 52, whenever x is 52, else 81.
The behaviour is identical when I open different files, btw. Could be different values on a different screen; I'll check that. But should be easily reproducable either way.
It seems that the bug that caused the window to fly off the visible screen when Window.move() was called has since been fixed somehow, so the position restored after restart should be identical now. Hopefully.