Open GoogleCodeExporter opened 9 years ago
This should work. Not sure why that option is not saved but I did notice the
same behavior sometime. Can you reproduce the issue every time?
Original comment by MeanEYE.rcf
on 13 Mar 2013 at 9:33
Yes, every time.
Original comment by tech@frontrowcomputer.com
on 13 Mar 2013 at 9:40
Okay. Try starting Sunflower from the terminal and let me know if there is any
output there when exiting normally.
Original comment by MeanEYE.rcf
on 13 Mar 2013 at 9:44
No, there doesn't seem to be. However, this was there at the beginning:
/usr/share/sunflower/application/accelerator_group.py:81: GtkWarning:
IA__gtk_accel_group_connect: assertion `accel_key > 0' failed
self._accel_group.connect_group(keyval, modifier, 0, self._handle_activate)
I also noticed that it started the way I described before.
However, one time before, I did notice it evidently saved the proper settings
and brought it back when re-opened. So maybe not everytime?
Original comment by tech@frontrowcomputer.com
on 13 Mar 2013 at 11:28
In my case it's rare for it to not save. Am still not sure what causes it.
After you upgrade to latest version, check then. Perhaps it's a version
specific issue.
Original comment by MeanEYE.rcf
on 13 Mar 2013 at 11:30
Okay, thanks.
Original comment by tech@frontrowcomputer.com
on 13 Mar 2013 at 11:33
Original comment by MeanEYE.rcf
on 18 Mar 2013 at 6:03
Also encountering this and for me it only breaks when the window is maximized,
otherwise it works fine.
Original comment by bmarin...@gmail.com
on 1 Apr 2013 at 6:45
Does it happen every time window is maximized?
Original comment by MeanEYE.rcf
on 1 Apr 2013 at 10:21
I had never tested my version 0.1a (54) as far as maximize-close or
normalize-close. They both worked fine and came back to exactly where they
were before. I even tried minimizing it from maximized. If I minimize it from
that size and close, it opens up maximized. That seems to be good behavior.
However, the normalize feature stops working at that point.
To fix that, one must grab the corner of the maximized window and create a
normalized size. Then the function starts working again to normalize or
maximize with the button.
Original comment by tech@frontrowcomputer.com
on 2 Apr 2013 at 6:00
Am not entirely sure issue with saving window position/state is related to
panel sizes.
Original comment by MeanEYE.rcf
on 2 Apr 2013 at 6:03
Sorry,I can't help there. Do you need any other testing?
Original comment by tech@frontrowcomputer.com
on 2 Apr 2013 at 7:10
Thanks for helping out. I can't remember anything specific to test right now,
but I'll be sure to let you know once I do. If you do feel like testing cloning
main repository and testing/using version before its release is the best way to
help with new features.
Original comment by MeanEYE.rcf
on 2 Apr 2013 at 7:37
Steps to reproduce in my case, happens every time:
#1 Open sunflower-fm
#2 Maximize
#3 Move the handle to the center
#4 Close & open sunflower-fm -> maximized but the handle moves to the right
What seems to be happening on re-opening is that the window is restored to the
original geometry, the handle is in the position that is was when maximized and
when maximize is called it is moved relative to the new window size
(maximized). What maximization does seems to be ok, so a possible solution is
for the handle to be saved relative to the geometry not the maximized state.
Original comment by bmarin...@gmail.com
on 3 Apr 2013 at 9:10
Okay, thanks. This helps a lot.
Original comment by MeanEYE.rcf
on 3 Apr 2013 at 12:05
This should be fixed.
Original comment by MeanEYE.rcf
on 11 Apr 2013 at 12:05
Original comment by MeanEYE.rcf
on 16 Apr 2013 at 1:22
Original issue reported on code.google.com by
tech@frontrowcomputer.com
on 13 Mar 2013 at 9:30