Summary: | SHIFT key doesn't change size | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Luciano <eulucianosalomoni> |
Component: | Brush Engine/Shape | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | hrittik.lone.wolf, rebuilderster, scottpetrovic, tamtamy.tymona |
Priority: | NOR | ||
Version First Reported In: | 4.2.5 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Luciano
2019-08-03 08:57:21 UTC
I this would need some discussion to figure out what we would want to do with it. Holding down shift does different things with different tools, so making all tools do brush resize would collide with other shortcuts. For example, holding down SHIFT after clicking make the rectangle tool constrain to a perfect square. Holding Shift after clicking the polygon tool closes the shape after another tool. I see where you are coming from with making the shortcut consistent across tools, but we would need to figure out how to remap or change the existing shortcuts that already use shift. Hi Scott. Thanks for your time. I think I couldn't explain my idea or I didn't understand what you explained (I'm not a English speaker). You are right about the consist proportion function. But notice that it works when you hold [SHIFT] AFTER the click. CLICK>SHIFT>DRAG My point is to resize the brush - by holding [SHIFT] - BEFORE the click. SHIFT>CLICK>DRAG Now, holding [SHIFT] before click in shape tools does nothing. So I think filling this "nothing" with the resize function could be a nice idea. Hope my words made sense now. Is anyone working on it? I was talking to some developers in the IRC and got to know that the brush size feature is implemented in kis_change_primary_setting_action.cpp file. Should I make changes in the file? Setting to wish, since it's about a new behaviour (since it will be a new behaviour for those tools). @Hrittik Das no, no one is working on it at the moment. Are you still interested? *** Bug 477351 has been marked as a duplicate of this bug. *** |