SUMMARY I've set two different brushes to Shift+E and Shift+Q. I set the Shift+E opacity to 24%, but after changing to Shift+Q while drawing rather rapidly, my Shift+Q turned to 24% Opacity. Might be because of Old computer from 2011, 2GB ram, and rather slow. STEPS TO REPRODUCE 1. Ten brush script, two different brushes, two different keybindings. 2. Changing Opacity setting on either. 3. Change while drawing, switches Opacity between brushes. OBSERVED RESULT Minor misshap, happened 4 times out of 25 times. EXPECTED RESULT Switches between opacity on the brushes. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Downloaded Krita 5.0 Beta. one hour before this post.
Can you check whether "temporarily save tweaks to presets" is enabled in the brush editor?
Created attachment 141585 [details] 0240C2AB91094E22B88F2E8F3D864B8D.png Hi! And good morning. ---Response to bug report--- Gave it a quick check, and yes, it is currently checked for both the brushes I was currently using at the time. I’ve linked both the brushes and their settings here. I hope it’s either a mistake from my part, if that’s the case, I’m very sorry. Hope you have an amazing day ahead of you. Stuck Dancing. [cid:image004.png@01D7AAEC.79A8FA40][cid:image005.png@01D7AAEC.79A8FA40] From: Halla Rempt<mailto:bugzilla_noreply@kde.org> Sent: Thursday, September 16, 2021 11:13 AM To: ATGortz@hotmail.com<mailto:ATGortz@hotmail.com> Subject: [krita] [Bug 442500] Ten Brush script, wrong opacity https://bugs.kde.org/show_bug.cgi?id=442500 Halla Rempt <halla@valdyas.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |halla@valdyas.org Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Halla Rempt <halla@valdyas.org> --- Can you check whether "temporarily save tweaks to presets" is enabled in the brush editor? -- You are receiving this mail because: You reported the bug.
Created attachment 141586 [details] 851ED30A2B274A479F4A81D42026A2DA.png
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
I'm sorry for forgetting about this report. I cannot reproduce the issue myself, and I do know a lot of this code has changed since 5.0.0, so I'm afraid I'll have to close the report.