In Windows The Frame Position Is Not Saved On Close #59

Closed
RobertBColton opened this Issue Jun 1, 2013 · 2 comments

Comments

Projects
None yet
1 participant
@RobertBColton
Collaborator

RobertBColton commented Jun 1, 2013

Yep LGM memorizes the last position and maximized state fine on Linux for me but never does in my Windows VM, and other forum members are saying it don't do it on Windows either...

http://enigma-dev.org/forums/index.php?topic=1279.0

This is regarding the main LGM frame not any of the little MDI ones, those are fine.

@RobertBColton

This comment has been minimized.

Show comment
Hide comment
@RobertBColton

RobertBColton Apr 17, 2014

Collaborator

This issue was just properly fixed by not creating FramePrefsHandler until directly after the main frame becomes visible, it effectively resolved the issues and the original patches by myself are now removed.

Collaborator

RobertBColton commented Apr 17, 2014

This issue was just properly fixed by not creating FramePrefsHandler until directly after the main frame becomes visible, it effectively resolved the issues and the original patches by myself are now removed.

@RobertBColton

This comment has been minimized.

Show comment
Hide comment
@RobertBColton

RobertBColton Apr 12, 2016

Collaborator

Testing on the new stable branch I am able to reproduce it but the original patch to fix it by me was not even necessary.

I can reproduce it with the following sequence of events.

        frame.setVisible(true);
        frame.pack();

I figured this out by reviewing 143fce7 which is the first commit to master where the issue exists. When I implemented look and feels I was setting the look and feel after setting the frame visible and my look and feel method that I adapted from Oracle's website included frame.pack(); which is supposed to be called before a frame is made visible.

Owner@BEDROOM-DESKTOP ~/documents/eclipse workspace/lateralgm (stable)
$ java -version
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)

Collaborator

RobertBColton commented Apr 12, 2016

Testing on the new stable branch I am able to reproduce it but the original patch to fix it by me was not even necessary.

I can reproduce it with the following sequence of events.

        frame.setVisible(true);
        frame.pack();

I figured this out by reviewing 143fce7 which is the first commit to master where the issue exists. When I implemented look and feels I was setting the look and feel after setting the frame visible and my look and feel method that I adapted from Oracle's website included frame.pack(); which is supposed to be called before a frame is made visible.

Owner@BEDROOM-DESKTOP ~/documents/eclipse workspace/lateralgm (stable)
$ java -version
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment