Bug 392196 - Brush preset blacklist adding a "~" symbol on windows which won't work
Summary: Brush preset blacklist adding a "~" symbol on windows which won't work
Status: RESOLVED DUPLICATE of bug 393191
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: 4.0.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Halla Rempt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-22 21:04 UTC by ZeroFrost
Modified: 2018-05-08 11:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Marked in red presets appeared after overwriting oryginal preset and restarting Krita (391.12 KB, image/png)
2018-03-22 21:04 UTC, ZeroFrost
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ZeroFrost 2018-03-22 21:04:59 UTC
Created attachment 111563 [details]
Marked in red presets appeared after overwriting oryginal preset and restarting Krita

Changing any settings of any Brush preset and pressing "Overwrite Brush" Creates duplicat of overwrited preset after restart of krita.

Pressing Overwrite 10 times crates 10 copies of preset all with the same name.
Some of duplicated presets cannot be removed by "delete resource" button.
Comment 1 Scott Petrovic 2018-03-22 21:24:21 UTC
I can confirm this bug. 

Developer: This might be specific for Windows. I checked the blacklist file and it is putting a "~" symbol at the start of the blacklist file.   It doesn't appear Windows understand that character with file paths. 

Bug Filer: For future reference to help the devs try to write a report like this to make it easier to fix

Steps to reproduce
1. Create a new document
2. Open the brush editor
3. Change the brush size
4. Click "Overwrite" to save the brush
5. Close Krita and Restart Krita

Actual Results:
There are duplicates of the brush.

Expected Results: 
There are no duplicates shown on the brush.
Comment 2 Scott Petrovic 2018-04-16 15:31:48 UTC

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