search

Azaret / superputty

Automatically exported from code.google.com/p/superputty
MIT License
0 stars 0 forks source link

New Option: "Always start maximized" #144

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I would like the option to always start maximized in addition to "Restore 
Window Size and Location". Of course only this new option or Restore Window 
Size should be allowed.

Original issue reported on code.google.com by breker.c...@gmail.com on 18 Jun 2012 at 9:19

GoogleCodeExporter commented 9 years ago 
The reason for this enhancement request is that since one of the last versions 
SP remembers that the window was not maximized when using "Exit SuperPutty" in 
the context menu of the system tray icon or using "Close" in the windows 
default context menu when SP is mimimized to the task bar. So on the next start 
SP is not started maximized. The behaviour was different in earlier versions.

Original comment by breker.c...@gmail.com on 18 Jun 2012 at 9:36

GoogleCodeExporter commented 9 years ago 
Why not set your shortcut to Maximize and it'll start maximized every time even 
if last time was not maximized? Sorry, am I misunderstanding your request?

Original comment by djtrem...@gmail.com on 18 Jun 2012 at 12:35

GoogleCodeExporter commented 9 years ago 
Admittedly I didn't think of setting my program icon to maximized window. 
Thanks for the tip.

Original comment by breker.c...@gmail.com on 19 Jun 2012 at 8:40

GoogleCodeExporter commented 9 years ago 
When I use the workaround of setting the program icon to start as maximized 
window the option "Minmimze to Tray" doesn't work any more: When trying to 
restore from minimized the SuperPutty window flickers for some time and 
afterwards the task bar icon is missing. So that is not an acceptable 
workaround.

Original comment by breker.c...@gmail.com on 20 Jun 2012 at 1:24

GoogleCodeExporter commented 9 years ago 
Issue was with the fix I did for issue 138.  If minimized, i was forcing it to 
normal...didn't realize the "this.lastNonMinimizedWindowState" was being 
tracked.

Fixed in 1.3 branch.

Merging this issue into 138...really a bug in my fix

Original comment by btatey...@gmail.com on 22 Jun 2012 at 12:42