Bug 446261 - Workspaces save as window layouts and do not function.
Summary: Workspaces save as window layouts and do not function.
Status: RESOLVED DUPLICATE of bug 443717
Alias: None
Product: krita
Classification: Applications
Component: Dockers (other bugs)
Version First Reported In: 5.0.0-beta2
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-30 00:32 UTC by dragonheart2497
Modified: 2021-11-30 00:36 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dragonheart2497 2021-11-30 00:32:11 UTC
I attempted to save a workspace on Krita 5.0 beta 2, but the name I gave it appeared in the window layouts list instead. When attempting to open the workspace, it did nothing. Previously existing workspaces and layouts are functional. 

The workspace I created  appeared in the correct list and functioned after closing Krita 5, opening Krita 4, then reopening Krita 5- it may actually resolve by simply closing and reopening Krita 5 without the Krita 4 step, but I haven't tested that out. 


STEPS TO REPRODUCE
1. Modify workspace
2. Open workspaces/layouts drop down, type name into first "insert name" field
3. Save workspace

OBSERVED RESULT
Name appears in window layouts list and does not function. 

EXPECTED RESULT
Name appears in workspaces list and opens desired layout when clicked on. 

SOFTWARE/OS VERSIONS
Windows

ADDITIONAL INFORMATION
When I reopened Krita 5 the workspaces that glitches in the previous session work but the issue is still there when making new workspaces.
Comment 1 Tiar 2021-11-30 00:36:43 UTC
This should be already fixed in the recent Krita Plus build (download from the download page on the website). It would be a good idea to move to that build so you know which bugs are still relevant. (There should be a new beta soon as well).

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