Page 1 of 1

0.51 Win7: Window maximized state

Posted: Fri Jun 29, 2012 6:10 pm
by Brisq
XnView would not remember that window was maximized. If I start with a file (start in fullscreen is on) and then leave fullscreen, window will be small and in the top left corner. If I resize it before closing, next time I launch a file the window will be of a new size. However, maximizing window before leaving has no effect on the next launch, as it will open in a not-maximized window.
If I start using .exe, it will remember maximized state correctly, however next launch from file resets size and position to a small window in the top left corner.

Unchecking "Fullscreen when starting with a file" solves the problem but is not very convenient.

Problem persisted from early builds.
Windows 7x64, UAC off

Re: XnView 0.51, Window maximized state

Posted: Fri Jun 29, 2012 9:12 pm
by xankazo
Yeah, I can confirm this.

Re: XnView 0.51, Window maximized state

Posted: Wed Jul 25, 2012 3:28 pm
by kufer
Create a shortcut to xnview.exe anywhere in system and edit it to run program maximized. Then run it and close it.
From now it will remember last state as maximized.

Worked for me :)

Re: 0.51: Window maximized state

Posted: Tue Oct 02, 2012 8:46 am
by xnview
I can't reproduce with 0.51.

* start xnview with a file (open in fullscreen)
* ESC, and here the size is not correct???

Re: 0.51 Win7: Window maximized state

Posted: Mon Nov 12, 2012 1:39 pm
by Rebellious
Same problem here, v0.51Linux-64, though It worked ok sometimes . If app is maximized then closed, when app reopens treeview window width is not restored. Seems to have something to do with starting with command line. If app is not maximized (restored) the control size is restored properly on startup.

Re: 0.51: Window maximized state

Posted: Sun Oct 06, 2013 7:57 pm
by CreativeWorld
Same problem on 0.61 / Win8.1 x64.
xnview wrote:* start xnview with a file (open in fullscreen)
* ESC, and here the size is not correct???
It remembers the window position and size, but maximized state seems to be ignored completely. Happens only with the described scenario after fullscreen > view mode transition - the resulting window is never maximized. Browser mode doesn't have this issue.