Bug 396038 - GIT ae24634: Docker size configuration is lost upon each session
Summary: GIT ae24634: Docker size configuration is lost upon each session
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Dockers (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-01 05:26 UTC by Isaac Zuniga
Modified: 2018-09-28 16:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Zuniga 2018-07-01 05:26:14 UTC
I'm not sure when this began, but I just started noticing it in recent days. I have a video showing it off right here: https://drive.google.com/file/d/1ZlsksdJhrQbOZPXGbWwlNHlqneUQM3_c/view?usp=sharing

If I add new dockers, it remembers which ones are there, but the sizes are all lost. I'm not sure if this is a bug or a corrupt configuration file somewhere. (I already tried deleting all the %appdata% folders.)
Comment 1 Halla Rempt 2018-07-10 13:52:53 UTC
Hi Isaac,

Krita's settings are here: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration -- and the kritarc file is where the workspace setup is saved.

For me, on Linux and Windows at least, the dockers' sizes are correctly restored, btw..

What happens if you save your workspace setup as a workspace file (with the right-hand toolbar button). Does that restore correctly?
Comment 2 Isaac Zuniga 2018-07-10 16:40:22 UTC
(In reply to Boudewijn Rempt from comment #1)
> Hi Isaac,
> 
> Krita's settings are here:
> https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration -- and
> the kritarc file is where the workspace setup is saved.
> 
> For me, on Linux and Windows at least, the dockers' sizes are correctly
> restored, btw..
> 
> What happens if you save your workspace setup as a workspace file (with the
> right-hand toolbar button). Does that restore correctly?

Kind of, but doing so just showed off what the problem may be. It seems Krita is forgetting what the previous workspace was before it closed. I have a video showing that right here:

https://drive.google.com/file/d/1xjYlSjyUownJL7GeWGvWFnlEnAqlkKcb/view?usp=sharing

All I do is pull out a few of the dockers so they're wider, and Krita cannot even remember that from one session to another. Fortunately, because I created a workspace file, I can always refer back to that to "tell it" what I want, though, I'd have to do that every session. It doesn't seem that Krita remembers it anymore.
Comment 3 Halla Rempt 2018-07-10 16:58:57 UTC
Hm, but krita doesn't actually have an active workspace -- after selecting, say, Minimal, Krita doesn't remember the current workspace is "Minimal", but remembers the configuration of dockers and toolbars, and restores that.

What I'm seeing here is that the workspace seems to save correctly, and can be restored, but the current window configuration doesn't get restored on a restart, and that's pretty strange, since it works for me on Windows and Linux.
Comment 4 Andrew Crouthamel 2018-09-28 03:08:35 UTC
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 set the bug status 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!
Comment 5 Isaac Zuniga 2018-09-28 16:48:31 UTC
Thanks for letting me know Andrew.

This ticket can be closed, because this issue no longer exists like it used to, not even in the recent git builds.
Comment 6 Andrew Crouthamel 2018-09-28 16:53:52 UTC
That's great, thanks the update!