Created attachment 120532 [details] sensitivity brush to move tool SUMMARY: Since the update to krita 4.2 I've got some issues with the program and I thought I should report them to you. First of all I love the new addition you did, where I can see if I'm adding or substracting something to my selection. But the option to move your selection while you're selecting something is rather inconvenient. If you're too close to the line you're going to shift your selection. while working on smaller areas it happens a lot and I had to adjust my selection everytime to it's original place. The same problem goes with the guidelines you can drag from the left and upper side of your toolbars. if you're working "near" the line it's switchs from pen to move tool. And the gap where it starts to switch is rather large. Another issue, but that's something I also had with the previous version, is renaming and adding an icon to a new created brush/stamp. I followed the tutorial from David Revoy (deevad). But after creating my brush the names and icons got all mixed up with the ones I already had. And I have something I would wish for in Krita: a button or option where you can reset krita to it's default settings including resetting roaming/ app data. As I mentioned before, I had problems to create a brush and during the process it delet an existing brush which I wanted to get back. To do that I had to insert the desired brush into the file "app data". I took me a while to get to that point, so I'm suggesting to add an easier way to do that. Thanks for taking your time to read this. Best regards
Hi, please report only one issue for each bug report. With 4 different things its impossible to work with them properly. Pick one, edit and make new bug reports for the other 3. - Selection: it's not clear how you are doing the selections, please elaborate more on the process you follow. I don't get issues with editing selection and move since the move action is not activated if a selection modifier is active. - The gap is indeed quite large to allow easy manipulation of guides. Once you are finished editing guides it is best to "lock guides" - Weird, but it might be realted to the resource manager bugs. I get no issue like that. - could be.
Created attachment 120552 [details] lasso tool.jpg Hello, thanks for replying, even though my bug report submission was incorrect. I'm not sure if I'm allowed to reply directly via this e-mail, but I wanted to give an answer to this existing correspondency. When I'm doing selections I'm using the free lasso tool and select an area. Most of my works have very detailed artline so I can't select everything I want with a rough selection. So I go this way:1. rough selection 2. zoom in for correcting my selection After that my selection is complete and the way I want it to be. And while working I noticed that the selection can be moved while using the lasso tool. If I'm in my workflow and don't pay attention I'm going to shift my selection by accident. I tried to make a picture of it, but I don't know if it's displays the issue well enough. (Taking a screenshot does not work, the cursor will not be displayed this way) Since reporting several bugs at once is not possible, I'll end my reply to you here. For the brush/stamp problem I'm going to open a new bug report. I attached two pictures to this e-mail. Thanks again for taking your time to read this.best regards *Gesendet:* Montag, 03. Juni 2019 um 20:56 Uhr *Von:* "vanyossi" <bugzilla_noreply@kde.org> *An:* laurinchen-007@web.de *Betreff:* [krita] [Bug 408260] selection, brush, reset kritahttps://bugs.kde.org/show_bug.cgi?id=408260 vanyossi <ghevan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ghevan@gmail.com --- Comment #1 from vanyossi <ghevan@gmail.com> --- Hi, please report only one issue for each bug report. With 4 different things its impossible to work with them properly. Pick one, edit and make new bug reports for the other 3. - Selection: it's not clear how you are doing the selections, please elaborate more on the process you follow. I don't get issues with editing selection and move since the move action is not activated if a selection modifier is active. - The gap is indeed quite large to allow easy manipulation of guides. Once you are finished editing guides it is best to "lock guides" - Weird, but it might be realted to the resource manager bugs. I get no issue like that. - could be. -- You are receiving this mail because: You reported the bug.
Created attachment 120553 [details] moving cursor.jpg
Hi, laurinchen-007! I'm sorry, I don't understand what the problem is :( When using Shift or Alt modifiers for selection, mode action is automatically disabled. Or you use the docker buttons to switch modes and do add/remove selection without any modifiers?
This only happens if using selection display mode as outline and tool option to add. But this is expected. To avoid this, a workaround: change the selection display mode to Mask, this avoids the use of the outline and avoids the cursor showing and moving the selection. This is best for doing detailed masking. Also you can change the appearance of the mask in Preferences -> display -> Selection Overlay [Select color and opacity of mask]. As for the move selection mode beign active on ouline mode when docker buttons are used. we will need to add an option to lock selection from move at all.
I think we need either change the title into something descriptive and find a good summary of the bug, or close the report. I haven't got any idea anymore what this is about :-)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!