Summary: | New palette are saved by default into the document: This is confusing behaviour. | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | David REVOY <info> |
Component: | Usability | Assignee: | vanyossi <ghevan> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bethabugaboo, ghevan, griffinvalley |
Priority: | NOR | ||
Version: | 4.2.3 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/kde/krita/commit/5c6b47cf6882ef384078ca733a105ebb27ff25ac | Version Fixed In: | |
Sentry Crash Report: |
Description
David REVOY
2019-07-23 13:41:30 UTC
Hi, I think new palettes are saved by default into the document, which IS very confusing default behaviour. Let's change it :) Oh ok :) Good to know for the palette being saved inside the document. True; not intuitive default. I found a workaround: I create a placeholder mypalette.gpl file ( a *.gpl file almost empty) in .local/share/krita/palettes/ , then I can edit it and all changes are done into a mypalette.kpl file next to it. (btw, the Drag&Drop of color-squares is a really cool new feature.) *** Bug 410319 has been marked as a duplicate of this bug. *** Git commit e1de013573f3d4b85d16b81eab2e561e058d3360 by Boudewijn Rempt. Committed on 01/08/2019 at 09:26. Pushed by rempt into branch 'master'. Allow the user to choose between saving and importing palettes locally or into the document M +34 -13 libs/ui/KisPaletteEditor.cpp M +1 -1 libs/ui/KisPaletteEditor.h https://invent.kde.org/kde/krita/commit/e1de013573f3d4b85d16b81eab2e561e058d3360 Git commit 5c6b47cf6882ef384078ca733a105ebb27ff25ac by Boudewijn Rempt. Committed on 01/08/2019 at 09:27. Pushed by rempt into branch 'krita/4.2'. Allow the user to choose between saving and importing palettes locally or into the document M +34 -13 libs/ui/KisPaletteEditor.cpp M +1 -1 libs/ui/KisPaletteEditor.h https://invent.kde.org/kde/krita/commit/5c6b47cf6882ef384078ca733a105ebb27ff25ac |