[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 Halla Rempt changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Halla Rempt --- This has been fixed with the resource system rewrite (tested with 891c50ad013d1a3ddbd144227a3f6d5ad944a704) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 Boudewijn Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |b...@valdyas.org Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Component|General |Resource Management -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 Tarn Faulkner changed: What|Removed |Added CC||ta...@wavetree.com --- Comment #9 from Tarn Faulkner --- I am seeing what I believe is the same bug (blacklisted brushes showing up in the Brushes Docker on Windows 10 installations of Krita 4.0.1), and have a relatively simple repro case. To reproduce: 1. Select any existing custom brush. Note that the custom brush should have been saved previously with "Save New Brush" and then Krita should have been restarted to avoid a different bug. 2. Edit brush slightly (I changed spacing value) and "Overwrite Brush". 3. Edit the brush slightly again and "Overwrite Brush". 4. Shut down and relaunch Krita. Result: Even though both backup brush files are written into the blacklist file, one of the them will still show up in the Brushes Docker. This is very problematic for users as doing multiple edits of a brush during one session can result in what look like many duplicates in the Brushes Docker. If I should have created a new bug for this please let me know. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 Scott Petrovic changed: What|Removed |Added CC||ran...@yandex.ru --- Comment #8 from Scott Petrovic --- *** Bug 393279 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 --- Comment #7 from ZeroFrost --- (In reply to Scott Petrovic from comment #6) > Could you explain what you mean? it definitely is not reading the ~ > correctly on my Windows 10 machine for finding a location. > > It decides to open the location in a web brower because it doesn't know what > to do with it. There may be some issues with "~" on windows but if that would prevent krita from recognizing paths to brushes blacklisting would never work (all paths start with ~) but in some cases blacklisting works perfectly with "~" in path (cases are describled as workarounds #1 and #2 in main ticket). I did many tests and Imo there is problem with how/when krita reads kis_paintoppresets.blacklist and apply it to memory, not how blacklist entites are written. Simple restarting krita fix issue and restarting doesnt change kis_paintoppresets.blacklist file at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 --- Comment #6 from Scott Petrovic --- Could you explain what you mean? it definitely is not reading the ~ correctly on my Windows 10 machine for finding a location. It decides to open the location in a web brower because it doesn't know what to do with it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191 --- Comment #5 from ZeroFrost --- (In reply to Scott Petrovic from comment #4) > This is the "~" blacklist problem that only exists on windows. Blacklist > files are getting a tilde character at the beginning which is messing things > up on Windows Windows reads"~" correctly overall. Issue occurs when brush was created and deleted(blacklisted) in one Krita session (without restarting Krita). Krita then proceed to ignore blacklist entries of those brushes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted ("~" at the start of Windows blacklist location)
https://bugs.kde.org/show_bug.cgi?id=393191
Scott Petrovic changed:
What|Removed |Added
Summary|[Brush-Presets] appear |[Brush-Presets] appear
|again if deleted/ |again if deleted/
|blacklisted |blacklisted ("~" at the
||start of Windows blacklist
||location)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted
https://bugs.kde.org/show_bug.cgi?id=393191 Scott Petrovic changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Summary|Brush preset blacklist |[Brush-Presets] appear |adding a "~" symbol on |again if deleted/ |windows which won't work|blacklisted Ever confirmed|0 |1 --- Comment #4 from Scott Petrovic --- This is the "~" blacklist problem that only exists on windows. Blacklist files are getting a tilde character at the beginning which is messing things up on Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted
https://bugs.kde.org/show_bug.cgi?id=393191 --- Comment #3 from Scott Petrovic --- *** Bug 392196 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted
https://bugs.kde.org/show_bug.cgi?id=393191 --- Comment #2 from ZeroFrost --- After inspection youre right. My pevious bug was about the same code problem just different steps to recrate it. I we cant merge those two we can close older one and leave this (i feel this is more indepth). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393191] [Brush-Presets] appear again if deleted/ blacklisted
https://bugs.kde.org/show_bug.cgi?id=393191 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Scott Petrovic --- Is this separate than your other bug report? It seems you are describing the same thing. https://bugs.kde.org/show_bug.cgi?id=392196 -- You are receiving this mail because: You are watching all bug changes.
