Version: 2.1b5 (using KDE 4.5.4) OS: MS Windows When starting up Kile, the window size is equal to my screen size (1280x800), but the window is not maximized. Hence, there's s tiny bit of Kile's window outside my screen. Which means I have to resize manually or maximize manually, every time. (When quitting, Kile does not remember its size for the next session, but this could be intended.) Reproducible: Always Steps to Reproduce: Start up Kile. Actual Results: Kile's window has the size as if it were maximized, but instead it is not maximized, placing part of the window outside the screen, forcing me to manually resize or maximize the window at every startup. Expected Results: There would be several ways to fix this: starting in a maximized window, starting with a smaller windows size than screen size, remembering the last view on exit, ...
This seems to work fine here, i.e. the size of the main window is remembered across restarts. It happens sometimes that the parts of the window are outside of the screen when Kile is starting up, but the size hasn't been changed. Hhhhmmm, are you maybe using any special utilities that would have an influence on the size of windows?
Oops, it seems my report was only half correct. Indeed, Kile does remember its window size between across. I don't know how I could miss this, sorry for that. It does however not remember the windows status. For example, if I maximize the Kile window and then quit, Kile will startup with the size of a maximized window, but will not be maximized (and hence part of it will be outside the screen). I don't know if this is easy to solve, but if it is, it would be nice. :-)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!