Bug 349322 - Workspaces' docker in latest Krita release doesn't show up anything
Summary: Workspaces' docker in latest Krita release doesn't show up anything
Status: RESOLVED DUPLICATE of bug 349026
Alias: None
Product: krita
Classification: Applications
Component: Dockers (other bugs)
Version First Reported In: git master (please specify the git hash!)
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-18 09:11 UTC by MichalG
Modified: 2015-06-19 07:34 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MichalG 2015-06-18 09:11:07 UTC
When playing around with latest Krita build for Windows (2.9.5) I found a little irritating bug regarding workspaces (*.kws).
Every time I try to open onscreen button "select a workspace", it does show nothing (i.e.there is just empty subwindow inspite I have many templates in proper place!). It allows, however, to choose any workspace, by browsing it on the disc.
And when I choose any template, it didn't work at all and all windows on the screen stay the same.
Isn't it something to fix, anyway?
Now I use Intel i5, on Win7 64-bit and Intel gfx-card.

BTW.  It turned out this bug appears on another computer I use (Win7 64-bit and Krita version 2.9.5). There is empty workspace subwindow and no chance to alter workspace by loading anything related....


Reproducible: Always


Actual Results:  
No expected behaviour

Expected Results:  
Effortlessly using (swapping/loading/saving) selected workspaces
Comment 1 Halla Rempt 2015-06-18 17:38:04 UTC
Hi Michal,

Are you using Krita with a translation active? If so, it's probably be the same issue as with bug 349026
Comment 2 MichalG 2015-06-19 07:25:24 UTC
Well, after checking out I can confirm it is the same issue!!! :o
Switching to "default" (English) will bring back proper work for Workspaces' docker.

So it looks like the bug is not new - why it hasn't been resolved so far???  :-\
Comment 3 Halla Rempt 2015-06-19 07:34:00 UTC
Because there are 315 open bugs and because I only saw the bug report yesterday? Bugs don't fix themselves automatically, people have to spend time on it, and there's only so much time in a day!

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