Restore from maximized mode issue

[Klaas]

Pierre, no - as for the best I can say... Since at least 2011 I installed every upgrade of XnView MP under Linux and Windows as soon as I got note of it, and I work with your wonderful software on a daily basis on both OSs. But I only realized that bug after I installed 0.60 under Win 7 - no such problems with the Linux version (0.60 under Ubuntu 13.04).

Edit: I almost exclusively use MP in a maximized Windows and only realized the problem when tying to change Layouts, which I do frequently...

[xnview]

Pierre, no - as for the best I can say... Since at least 2011 I installed every upgrade of XnView MP under Linux and Windows as soon as I got note of it, and I work with your wonderful software on a daily basis on both OSs. But I only realized that bug after I installed 0.60 under Win 7 - no such problems with the Linux version (0.60 under Ubuntu 13.04).

So you choose a size for XnView, save Layout A
Maximize it, save layout B
And if you change between Layout A<>B, you have the problem?

[Klaas]

Every "restore layout [X]" results in complete minimizing of a maximized window as shown in the screenshots abowe and a completely cluttered/destroyed layout... Even with newly created and saved (under .60) layouts in Windows. (As mentioned before: no problems under Linux...)

[xnview]

Every "restore layout [X]" results in complete minimizing of a maximized window as shown in the screenshots abowe and a completely cluttered/destroyed layout... Even with newly created and saved (under .60) layouts in Windows. (As mentioned before: no problems under Linux...)

I can't reproduce on windows 7 x64. Could you send me the layout.dat (of your maximized state)??

Is it the way you use?
* start XnViewMP
* save layout A
* maximize, save layout B
* restore layout A => good?
* restore layout B => not good?

[Zheitk]

*Start XnView MP
*Maximize it & adjust the layout to your taste
*Save "Layout A"
*Restore "Layout A"

2013-07-13 [13_34_59].png (185.69 KiB) Viewed 1960 times

You can appreciate how the whole interfaz shrank, the max button is still activated and the frame is "unresizable"
Some files to test:

default.bar + layout1.dat.zip

(1.02 KiB) Downloaded 88 times

[Klaas]

Thanks, Pierre, for your careful instructions, I'm sorry for my rather belated reply - and no, it still doesn't work. Every effort to restore a layout results in strange "window chaos" as indicated by Zheitk: At first the maximized window shrinks to about on third of the screen, the "reduce" button [English designation? I use the German version of Win...] is still there, and the window is not resizable manually anymore. If I click the mentioned button, the window finally shrinks to the size of playing card as show in the shots on this thread's first page. And if I click the "maximize" button (which is then there again) the window indeed maximizes - but with a completely cluttered layout.

And I also tried the Win-32-Bit version of MP .60 - the same problem (or at least very similar one, Im not sure at the moment) )...

[CreativeWorld]

This problem does not seam to have anything to do with layouts,
at least not for me in linux mint 15 32bit.

I deleted everything in the .xnviewmp folder
the .ini, .db, .bar and .key files,
so that it works like when i first installed xnview mp v0.61.

The unmaximized window size when it starts up is 856x647.




The maximized size is 1920x1175,




if i quit xnview mp while it's maximized, and start it again.



The folder tree view on the left and the info/preview panel at the bottom,
seams to have already been resized down so that they will fit in the tiny window below.

When i unmaximize the window,
it resizes down to 223x388.



It doesn't seam to remember the window size it had before it was maximized.

[Rebellious]

This appears to be the same problem as I posted in a new thread a few days ago:

http://newsgroup.xnview.com/viewtopic.php?f=62&t=28510

I also posted to another existing thread sometime last year, on the same bug.

Form_resize events can be a pain, especially multi-platform

[GeorgD]

FYI: Why is there this problem, which in the version 0.64 looks like a dupe of this issue.