"Maximized" window misses "status bar" at next opening of file

[worms_x]

This is still present in rev21009 (2009, March 29th) and has been going on for a while. I'm running Windows XP.

Steps to reproduce:
- Open a file with Inkscape
- Maximize the window (so it occupies the whole screen less the Windows task bar)
- Save and Quit

- Reopen the file
- The window position is restored correctly, except that the window is not "maximized", there is a space above it, and the status bar is not showing at the bottom.

I am filing this bug although this may be related to:
https://bugs.launchpad.net/inkscape/+bug/195683
and/or
https://bugs.launchpad.net/inkscape/+bug/283152
because the described behaviours seem different

[Alvin Penner (apenner)]

running Windows XP and build 21024, I can't reproduce this behaviour.
In the Inkscape Preferences, I had to specify "Remember and use last window's geometry" to get this to work normally.

[worms_x (wormsxulla)]

To my understanding, there are 3 options for saving and restore of windows

1) Don't save window geometry
2) Remember and use last window's geometry
3) Save and restore window geometry for each document

My bug report was incomplete, of course the option I have is 3) save and restore window geometry for EACH document.
So I expect that if I maximize a document, then save and exit, next time I open it, it will be maximized (and not missing the status bar as explained in the bug)

Of course, with this option 3), and if I have not modified anything else, Inkscape will open in a small window size for a blank document (which is OK). I then adjust the window size as needed for the document.

So comment 2) from Alvin doesn't apply to this bug: I do not want a document to have the same size as the last one I used, be it mazimized or not.

Anyway, I think this might be fixed with fix of bug https://bugs.launchpad.net/inkscape/+bug/168422 , which unfortunately I hadn't find when I searched for a similar problem before reporting.

Can someone with a fresh build on Windows XP verify it's fixed as of rev 21407 ? Thanks

[jazzynico (jazzynico)]

Reproduced on WIndows XP sp3 and rev. 20869.
But NOT with rev. 21524.
Fix confirmed!