Bug 395819 - Assistant Tools Color & Opacity (one for all assistants) - unsaved to .kra file
Summary: Assistant Tools Color & Opacity (one for all assistants) - unsaved to .kra file
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tool/Assistants (other bugs)
Version First Reported In: 4.1.0 beta
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-24 16:40 UTC by Tiar
Modified: 2018-07-27 11:57 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 Tiar 2018-06-24 16:40:34 UTC
The global color and opacity of assistant tools are not saved to .kra file.

Steps to reproduce:
1) Create new document
2) Create two assistants somewhere
3) Change the ('global') color and/or opacity of one of the assistants, then for another use "Custom color" and set the ('local') color and opacity
4) Save the file, close, open again

Actual results:
5a) The assistant with the local color looks the same as before reloading; the assistant with the global color returned to the default color (light grey) and opacity (100%).

Expected results:
5b) Both assistants have the color and opacity set before saving, closing and reopening the file.

There are two workarounds:
1) Choosing a custom color for every assistant tool - but it is time-consuming and choosing a color once would be better; also the default color of the custom color doesn't change to the last used, which contributes to the time-consumness (and annoyance) of the solution
2) Changing the global color every time after opening a file - still, choosing a color once would be better
Comment 1 Tiar 2018-06-24 16:47:38 UTC
Probably relevant: bug #382805
Comment 2 wolthera 2018-07-27 11:57:39 UTC
This should be fixed in 4.1(https://krita.org/en/item/krita-4-1-0-released/), if that is not the case, please reopen this bug!