Bug 359592 - remember window state // or: start maximized
Summary: remember window state // or: start maximized
Status: RESOLVED FIXED
Alias: None
Product: trojita
Classification: Unmaintained
Component: Desktop GUI (show other bugs)
Version: 0.6
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Trojita default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-20 06:12 UTC by msjasinski
Modified: 2016-02-22 13:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
This is how it often looks in 0.6. (57.79 KB, image/jpeg)
2016-02-21 12:34 UTC, msjasinski
Details
This is how it looked on second program initiation. (61.30 KB, image/jpeg)
2016-02-21 12:39 UTC, msjasinski
Details
This was how it looked on 3rd initiation, but on 4th we were back to scenario 1 (Clipboard1.jpg) (62.71 KB, image/jpeg)
2016-02-21 12:40 UTC, msjasinski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description msjasinski 2016-02-20 06:12:33 UTC
The application does not remember its window state and often starts unmaximized (part of the window going out of the visible screen). This happens even if I tick Preferences: Start Maximized.

Reproducible: Sometimes
Comment 1 Thomas Lübking 2016-02-20 14:51:27 UTC
Trojitá does restore its geometry.

=> Is the problem strictly related to initial maximization?

And why is a "part of the window going out of the visible screen"? Is the window too huge for the screen or does it take a position inside the screen that pushes the bottom-right corner outside?

(Please notice that probably no active developer uses windows, so we rely on your information here)
Comment 2 Jan Kundrát 2016-02-20 16:01:37 UTC
Also please tell us where did you get Trojita from. If you used the official installer, the 0.6 release was the last one which used Qt4, while the new development is now on Qt5 only. Could you please use a newest snapshot from http://ci-logs.kde.flaska.net/binaries/trojita/win32/rebuilddep/?C=M;O=D and try to reproduce?
Comment 3 msjasinski 2016-02-21 12:34:33 UTC
Created attachment 97333 [details]
This is how it often looks in 0.6.

 UI is in Polish because there is no option to change localization during install or in the app (Trojita chooses system default).
Comment 4 msjasinski 2016-02-21 12:39:26 UTC
Created attachment 97334 [details]
This is how it looked on second program initiation.
Comment 5 msjasinski 2016-02-21 12:40:31 UTC
Created attachment 97335 [details]
This was how it looked on 3rd initiation, but on 4th we were back to scenario 1 (Clipboard1.jpg)
Comment 6 msjasinski 2016-02-21 12:44:30 UTC
The pics use 0.6, as explained above.

Then I used the latest snapshot (Trojita-Setup-v0.6-42-g75e05a1.exe   2016-02-08 07:54 	21M), as advised.

It seems to not have this problem, but it is too unstable to be used. It partly failed to connect to google smtp. I need more time to test it thoroughly.
Comment 7 Jan Kundrát 2016-02-22 13:18:06 UTC
(In reply to msjasinski from comment #6)
> 2016-02-08 07:54 	21M), as advised.
> 
> It seems to not have this problem

Thanks for testing, closing as resolved, then. Bugs in the Qt4 version are irrelevant by now, we are not going back there.

> but it is too unstable to be used. It partly failed to connect to google smtp. I need more time to test it
> thoroughly.

There is no difference in the SMTP implementation between the Qt4 and Qt5 builds. There might be a huge difference in, for example, the TLS handling in Qt5; please file a separate bugreport about that issue with more detailed information.