[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Halla Rempt changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 --- Comment #8 from Halla Rempt --- *** Bug 442493 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Andrei changed: What|Removed |Added CC||ilikeorange...@gmail.com --- Comment #7 from Andrei --- The default shortcuts of Ten Brushes "ctrl+alt+number" work fine in Krita Beta 5 but changing to something like "E" used to enable eraser mode doesn't change back the preset. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Ziyad Rahmani changed: What|Removed |Added CC||mziyad...@gmail.com Component|Shortcuts and Canvas Input |Scripting |Settings| --- Comment #6 from Ziyad Rahmani --- (In reply to stephen from comment #5) > (In reply to Halla Rempt from comment #3) > > No, only developers should change the status of a bug. > > > > Resolved/Worksforme means: it works for me, I cannot investigate this report > > anymore since there's nothing left for me to try and test or debug. > > New update : > The issue seems to be caused from the retrieval of brush settings from the > sqlite database of a previous Krita version. Especially coming from 5.0.0 > beta 1 to later versions. A break happens in the process apparently, causing > the brush history to not work as expected with the Ten brushes script. > I tried to completely remove any sqlite backup before starting Krita and the > ten brushes script worked fine. How to do that? I'm sorry, I don't have understanding about these things -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 stephen changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from stephen --- (In reply to Halla Rempt from comment #3) > No, only developers should change the status of a bug. > > Resolved/Worksforme means: it works for me, I cannot investigate this report > anymore since there's nothing left for me to try and test or debug. New update : The issue seems to be caused from the retrieval of brush settings from the sqlite database of a previous Krita version. Especially coming from 5.0.0 beta 1 to later versions. A break happens in the process apparently, causing the brush history to not work as expected with the Ten brushes script. I tried to completely remove any sqlite backup before starting Krita and the ten brushes script worked fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 --- Comment #4 from stephen --- (In reply to Halla Rempt from comment #3) > No, only developers should change the status of a bug. > > Resolved/Worksforme means: it works for me, I cannot investigate this report > anymore since there's nothing left for me to try and test or debug. Then I shall forward a screen recording of the issue at the very least. Just so that you understand it's really not working on my side. It doesn't happen with the first Krita 5.0.0 beta, but with the current 5.1.0 prealpha and current 5.0.0 beta builds, switching back to previous preset is not possible anymore. Recording video will be forwarded in the next message. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Halla Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 --- Comment #3 from Halla Rempt --- No, only developers should change the status of a bug. Resolved/Worksforme means: it works for me, I cannot investigate this report anymore since there's nothing left for me to try and test or debug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 stephen changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #2 from stephen --- (In reply to Halla Rempt from comment #1) > That works for me. Are you sure ? That doesn't work for me. I tried installing this version of Krita again but nope. So how do I make it works here. Saying that it works on your side isn't helping. This is the name of the setup file : krita-nightly-x64-5.1.0-prealpha-8376871fce-setup Also, what to do when it becomes "Resolved" "works for you" while it doesn't work for some other ? Should I even turn the status as "Reported" ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Halla Rempt --- That works for me. -- You are receiving this mail because: You are watching all bug changes.
