| Summary: | Imported .gpl palette disappear upon re-launch/re-open | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | pegasusearl |
| Component: | Resource Management | Assignee: | Halla Rempt <halla> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | griffinvalley, halla |
| Priority: | NOR | ||
| Version First Reported In: | 4.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | This is the gpl file I used for testing. From lospec website. | ||
|
Description
pegasusearl
2020-09-11 11:37:18 UTC
Ok, I think I actually fixed this one for 4.4, can you check Krita:Plus from the website? (In reply to wolthera from comment #1) > Ok, I think I actually fixed this one for 4.4, can you check Krita:Plus from > the website? Krita 4.4.0-alpha git(c00326b) The problem still present. The difference is now it does not ask me whether or not I want to save the palette to current document. The behaviour is similar to when I select YES to 'save to current document'. The palette disappear on re-launch but still present if we re-open project. while we are talking about palette docker, I also want to quote a post in the forum: "reducing the number of columns and rows erases colours; they don’t re-organise themselves, but instead are fully gone." or should it be separate bug report? There's already a bugreport for that, but it'll take a bit more brainpower from me on how to solve that one as it's a case of bad design in general. This is fixed in master (tested with 66812ef4f7) |