which is inconsistant,i feel,and even just too few steps to work. Yes there are other shorcuts (numpad+ and -),but I would use those if they fitted my workflow. 19:02:50 - Bollebib1: deevad, boud: my shorcuts go from 12-25-50-100 19:02:50 - Bollebib1: or 33-67-141 19:02:50 - Bollebib1: while my mouse does all of those steps 19:05:09 - Bollebib1: I guess I can see why a person might want to have less steps to press, but to me it seems like too steep a jump 19:05:47 - sKreamer: ::krita:: Krita General Help :: Re: Transform selection @ http://forum.kde.org/viewtopic.php?f=139&t=119085&p=299625#p299625 (by Charblaze) 19:05:56 - Bollebib1: and if you don't know what's happening you can't get 100% with the keyboard shortcuts (when on the 33-67-141 path) 19:05:59 - deevad: Bollebib1: both does here 13 - 17 - 25 - 33 - 50 -67 - 100 - 141 - 200 19:06:06 - Bollebib1: strange 19:06:25 - deevad: yes 19:07:21 - Bollebib1: also my krita crashes when I press alt+ctrl+LMB (without space) 19:07:33 - deevad: Bollebib1: when you say 'shortcut' ; do you mean default numpad+ and numpad- ? or custom ? 19:07:51 - Bollebib1: my shorcuts are on + an - I think 19:08:57 - Bollebib1: ah no 19:08:57 - Bollebib1: on of them is customized 19:09:08 - Bollebib1: but the other one isn't 19:09:25 - Bollebib1: so if that were the issue I would get more steps with that one,no? 19:10:02 - Bollebib1: but they're the non-numpad shorcuts though 19:12:11 - Bollebib1: deevad: used another keyboard ,and yes numpad does do all the steps 19:12:18 - sKreamer: ::krita:: Krita Tutorial & Resources :: Need SO Much Help ( new ) @ http://forum.kde.org/viewtopic.php?f=274&t=119088&p=299627#p299627 (by lollirot) 19:13:09 - Bollebib2 has left the room (Quit: Remote host closed the connection). 19:13:37 - deevad: Bollebib1: nice, I think there is enough info now for a bugreport :) 'Custom zoom shortcut should works like default numpad + and numpad - zoom […] Reproducible: Always
The reason of the bug was that the shortcut was defined in both kde's "Configure Shortcuts" and "Custom Input Settings" systems, so it was invoked twice. Rename the bug to not allow the conflicting shortcuts between "Configure Shortcuts" and "Custom Input Settings". Setting the same key combination in both systems should result either in error or in a warning
I have just started KDE hacking and I don't understand this bug. What do you mean by "Custom Input Settings"? do you mean "Input Settings" as in Configure Shortcuts -> "Shortcut" and "Alternate" list? or something else?
Their are two way to set shocuts one is over Setting->configure shortcuts... and the other is over settings->configure krita... and then canvas input settings in the dialog
Due to a discussion on IRC it looks like the following 6 shortcuts are duplicated ( double mapped) "BackSpace" "C" "Ctrl+[" "Ctrl+]" "Ctrl+A" "Ctrl+Alt+R" "Ctrl+Alt+S" "Ctrl+B" "Ctrl+I" "Crtl+Shift+A" "Crtl+Shift+D" "Ctrl+T" "Ctrl+U" "Ctrl+V" "H" : Note I think this one should be mapped to "K" "P" Its is very possible some of these mapping are correct and that they are context sensitive mappings, but is it possible to get someone in the know to verify them Thanks cajone
@cajone In my test they are context sensitive mappings. Some of them don't work though or are missing: "Ctrl+Alt+S", "Ctrl+Alt+A", "Ctrl+T", "Ctrl+V". "BackSpace" 1) [EDIT] Fill layer or area selection with background color 2) [OBJECTS] Remove selected point(s) (path editing) "C" 1) [TOOLS] Crop the image to an area... 2) [OBJECTS] Extend segment(s) points handles (path editing) "Ctrl+[" 1) [OBJECTS] Send object(s) backward in its layer 2) [IMAGE] Rotate canvas view to left "Ctrl+]" 1) [OBJECTS] Send object(s) forward in its layer 2) [IMAGE] Rotate canvas view to right "Ctrl+A" 1) [TEXT] Select all text (text editing) 2) [SELECT] Select all layers "Ctrl+Alt+R" 1) [TEXT] Justify (left and right justified) (text editing) 2) [TEXT] Align right (text editing) "Ctrl+Alt+S" 1) [FILE] Save incremental version 2) [TEXT](* not working) Open character and paragraph style manager dialog "Ctrl+B" 1) [TEXT] Toggle bold style in Multiline text editing 2) [FILTER] Open Adjust > Color Balance.. internal filter dialog "Ctrl+I" 1) [FILTER] Open Adjust > Invert internal filter dialog 2) [TEXT] Toggle italic style in Multiline text editing "Ctrl+Shift+A" 1) [TEXT](* not working) Deselect all text (text editing) 2) [SELECT] Deselect area selection "Ctrl+Shift+D" 1) [TEXT] Change writing direction in Multiline text 2) [SELECT] Reselect last selected area "Ctrl+T" 1) (???) 2) [TOOLS] Transform a layer or a selection "Ctrl+U" 1) [FILTER] Open Adjust > HSV Adjustment... internal filter dialog 2) [TEXT] Toggle underline style in Multiline text editing "Ctrl+V" 1) [EDIT] Paste selection 2) (???) "H" 1) [TOOLS] Decrease color lightness by 10 2) [TOOLS] Show color patches history in Advanced Color Selector "P" 1) [TOOLS] Select a color from the image or current layer 2) [OBJECTS] Convert shape(s) to path (editing mode)
I was kindof short in my opening post but I want to clarify that I'm in favor of context sensitive shortcuts.I don't mind double shortcuts for different but similar(or even dissimilar) if it makes sense and is clearly divided. A good example of this is Blender that has plenty of tools with same shortcuts ,but that only appear when using those shortcuts... But when you configure a shortcut you should perhaps be notified that a shortcut is being used. I would even argue now that you perhaps SHOULD NOT ban duplication of shorcuts. Merely notify them and offer the option to remove them but also the option to leave them alone. In TVPaint you can add 2 functions to the same shorcut to get a compound effect. As an example you can combine a 'layer select' function to a 'shake layer' function. the result is that when you select a layer,the layer shakes to alert you which layer. SO that could also be an interesting route. So I don't really know what needs to happen. At the very least there should be alerts. Besides that there are a few option like I described,which are open to implement however the dev feels like.
WISHGROUP: Larger Usability Fixes Making this a bug.
*** Bug 378041 has been marked as a duplicate of this bug. ***
Note: this also should check whether the user tries to assign a menu accelerator.
*** Bug 396487 has been marked as a duplicate of this bug. ***
*** Bug 410552 has been marked as a duplicate of this bug. ***
*** Bug 437130 has been marked as a duplicate of this bug. ***
Just going ahead and setting this to Krita 5.2.6 (from 2.8) as part of the Bughunt Month.