You know when press Ctrl+T to activate transform and then you have to go to the options to do the transform method you want?
How about having shortcut entries for each transform method ? And still you would be able to swap after as normal.
The objective would be if I have preference for one or two methods I would not need to use the options docker to swap out into it and I could just hit the shortcut to activate it.
I imagine this would speed up workflows related to photobashing as you insert images and transform a lot right after as it would not force you to go to the menu to get the correct method.
I donāt know how the transform is setup but I imagine making shortcuts for these would not be too hard to implement. Shortcuts is not quite the same as a entire feature.
I was watching a tutorial about concept artwork using photobashing and I was thinking krita can be better than this just a shortcut action here to skip menus.
would that not mean you would have to like hit (Ctrl+T) x 3 to get what you want? and if you miss click the amount would it not be harder to cycle back into the correct method? I feel that would have a gainned difficulty though.
a thing like a pie menu would solve it with just a single menu but you still would need the actions for it to be triggearble.
Yes, but you would only have to memorize one shortcut and it would still be quite fast to get what you want. Granted, you will probably do a few mistakes and have to cycle through again the first times you use it.
How would a secondary pie menu work? There is already a pie menu in Kritaā¦ would this one only appear over the docker?
That should be another function that allows people to correspond to multiple tools with one shortcut key. Then it will switch between several tools when pressed multiple times. Csp does this, and I think itās good. The design of the toolModifiers plug-in is also very good. It can press multiple times to return to the previous tool, which is also my favorite
In short, it does not conflict with the topic of the post
all shortcuts relay on the fact you have to memorize it. and having a shortcut for each means you could select the ones you use the most for it.
having Shift+T and Alt+T would be more efficient than having (Ctrl+T) x3 and (Ctrl+T) x5. At least I think so.
But hitting several times on a transform shortcut to cycle would not be a bad idea to not use the docker to switch after the first selection method and cycle through. This would make it harder to implement though.
Not opposed to this at all, but above all Iād like to be able to trigger the transform by just pressing āctrl-tā without having to press ātā first.
I think this [E: the discussion of the] proposal conflates three ideas:
Shortcuts for each of the transform modes
A shortcut for a transform modes pie menu
A transform cycle shortcut
I would see uses for with 1 and 2. Ultimately, like Blender allows, is that users should be able to configure it any way they want, be it with a pie menu or with direct shortcuts. Donāt need all the individual shortcuts? Donāt set them up as hotkeys and if you donāt need the pie menu, donāt map a key to the pie menu function.
E: Toggling shortcuts (3) would be fine by me if it is for tools and single button shortcuts, otherwise you might risk activating something you didnāt want to in the first place.
Would it be possible to take another look at this feature? More specifically, direct keyboard shortcuts for the following transform modes:
Perspective
Warp
Cage
Liquify
Mesh
These modes are incredibly powerful and to be able to activate them directly with keyboard shortcuts would allow for some really cool digital painting and photobashing workflows.
If youāre not using Android, you can access them via the plugin Shortcut Composer.
Otherwise, you should be able to write action files for calling them, I would be astonished if they werenāt accessible that way.
Thank you so much! I will take a look into creating action files. Is there a place to share those action files here on the forum? Under āResourcesā?
If you want to share them after creation, you should do it there. Iām just not sure if you should use Brushes and Bundles or Plugins as the category to put them in, I somewhat prefer the latter but donāt know where our administration would like to see them posted.
Shortcut composer adds those as actions. But it requires some very nasty python code to make it work and comes with issue that may not be fixable.
I donāt know what you mean by āadding action filesā - these are only the definitions that need an implementation - either in python or cpp.
As far as i know, the only reliable way of implementing that, is doing it in the kritaās source code, so I approve the initial feature request a lot.
I just tested it and my guess was wrong, or I have overlooked something doing it so quickly.
My guess was like I did it for Paste into Active Layer, for instance, or a few other things without own shortcut. As you know, you can find out action names and more using the Plugin Developer Tools or studying the source code, and I thought the same should be possible with these transform options, if you then create an action file for that specific action, to address it/point to it, you can call it via shortcut. But as said in the first sentence, whether I overlooked something or it is impossible.
Currently, I donāt have the time to check this, but right now it seems impossible. Should I find a solution, I let you know.
Thank you all for the detailed investigation! It sounds like:
Shortcut Composer has issues and requires complex workarounds.
Action files donāt seem to work for transform modes specifically.
This particular feature would need to be implemented in Kritaās source code itself.
@wojtryb - Since you mentioned approving the feature request, what would be the best way to submit this as an official feature request to the Krita development team? Should I post it in a different section of the forum, or is there a bug tracker/feature request system?
I really appreciate everyone taking the time to explore the technical possibilities! Thank you @Michelist for doing some tests to verify if action files would work.
You can create a wish bug at https://bugs.kde.org/, if you need more information on this, Iāll collect it for you, or search for wish bug and use my moniker @Michelist as further requirement, I made some postings on this topic.
But currently Iām busy with other things that will need time.
Thank you so much @Michelist! Thatās exactly what I was looking for. Iāll create a wish bug at https://bugs.kde.org/ and will search for your previous posts about wish bugs to understand the process better.
No rush at all, I completely understand youāre busy with other projects. I really appreciate all the help you and @wojtryb have provided, thank you!