Bug 429734 - window size no longer remembered on Windows
Summary: window size no longer remembered on Windows
Status: RESOLVED DUPLICATE of bug 429943
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 20.08.3
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
Depends on:
Reported: 2020-11-27 17:34 UTC by Jason Craig
Modified: 2020-12-07 18:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description Jason Craig 2020-11-27 17:34:43 UTC
The window size isn't remembered anymore on Windows. I do not know which version was installed previously so I'm unsure when this was introduced. I use the .exe installer from https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/ to get Kate. If there is a setting which controls this I can't find it.

1. Start Kate
2. Resize the window
3. Close Kate
4. Re-open Kate

The window size goes back to what it was in step 1.

The window should be the size it was in step 2.

Windows: 10
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Comment 1 Jean-Baptiste Mardelle 2020-12-02 10:18:58 UTC
We have a similar problem for Kdenlive on Windows, wondering if it is a KDE Frameworks bug. Can you check the .katerc file to see if some random characters are written in it ?
Kdenlive bug: https://bugs.kde.org/show_bug.cgi?id=429264
Comment 2 Jason Craig 2020-12-02 17:26:21 UTC
Yes, I can confirm that katerc (in [User]/AppData/Local on Windows if anyone is having trouble locating) has many such lines in the [MainWindow] section for Width, Height, XPosition and YPosition in various states of being cut off with strings like DISPLAY1 and \\ prepended e.g.

  \\ght 864=786
  \\ight 864=646
  \\th 1536=1010


  \\.\\ISPLAY1 Height 864=532
  \\.\\ISPLAY1 Width 1536=760
  \\.\\ISPLAY1 XPosition=448
  \\.\\ISPLAY1 YPosition=172
Comment 3 Nate Graham 2020-12-07 18:34:35 UTC

*** This bug has been marked as a duplicate of bug 429943 ***