Closed GoogleCodeExporter closed 9 years ago
Hmmm... it is up to the window manager to determine the location of the window,
windows in this case it
placing arora in that location. Saving and restoring the location is usually
begging for bugs and issues.
Original comment by ice...@gmail.com
on 28 Mar 2009 at 12:57
True, and I guess I'm reporting this bug hoping it will be fixed.
It is a usual expectation for Windows apps to restart maximized if they were
maximized
when closed. Arora must not be interacting properly with Windows/saving the
proper
details/not starting with proper parameters/whatever.
Can Arora be fixed to restart maximized if closed maximized on Windows?
Original comment by dhh...@gmail.com
on 28 Mar 2009 at 1:09
Yes it can be fixed, just adding some notes :)
Original comment by ice...@gmail.com
on 28 Mar 2009 at 2:28
This should already be fixed in git.
Original comment by cebywan
on 28 Mar 2009 at 4:26
Fixed in git (at least on linux).
Original comment by ice...@gmail.com
on 29 Mar 2009 at 3:13
Thanks! Fixed in Arora 0.6 for Windows.
Original comment by dhh...@gmail.com
on 30 Mar 2009 at 2:35
Issue 59 has been merged into this issue.
Original comment by faw...@gmail.com
on 16 May 2009 at 8:01
Original issue reported on code.google.com by
dhh...@gmail.com
on 28 Mar 2009 at 12:19