![]()
Thanks for the heads up. I should stop using my ārage-fueledā themed keyboard.
I think you missunderstand one fundemental point.
We have selection tools that use ctrl or shift or alt to manipulate the selection. Like moving it or locking its proportion.
Iām only talking about the polygon-selection-tool, and you never moved your selection there with any of those keys pressed. (as I recall, it also worked in the recent versions of krita like this)
When using the poly-s-tool, the only way to moove a selection is by hovering over it, and then click-n-drag.
Iām talking about the poly-s-tool and the modifiers in this stage:

When you have a selection in progress, pressing anything of those key mentioned above, it does not move the selection either.
So there is no collision.
I wish I had the competence to code and the time, but I do not.
Plus,
Application.action(āselection_tool_mode_addā).trigger()
Does this apply before starting a selection, or does it also apply before closing the loop?
(like in the picture above)
Thank you a lot for your time <3
These are my thoughts:
- All the selection tools need to function in the same way.
- If you allow choosing the selection action while making the selection, there gonna be clashes between choosing the selection action and activating some toolās specific action. That was the reason of the change. There was more than one bug related to that.
- Although the polygonal selection does not have specific actions at the moment, it may in the future. For example snapping to predefined angles was already requested if I remember well. That needs shift.
- This is the way other apps handle the situation as well. It is a good compromise that avoids weird issues.
- In my opinion one should not just add different tweaks to different places in the app based on some user likes.
- I think you have to try to adapt to this simple thing, which is standard behavior amongst drawing apps, and understand there are design or implementation decisions you have to adapt to for the better good.
Thatās why I asked here first, before making an request entry.
I think you have to try to adapt to this simple thing, which is standard behavior amongst drawing apps, and understand there are design or implementation decisions you have to adapt to for the better good.
If it would not break my flow I would. But it does, and I take my flow as serious, as you take the development serious.
And thatās fine. Course it sucks, but itās fine.
Thank you for your time, again tho <3
The script code works exactly as intended. It changes the selection mode at any time.
I understand you want your workflow preserved, and many others do too. Just look at the topic Take layer state into account in the undo history
Thatās why I tried to give you a compromise. A different set of shortcuts (not perfect) but at least you workflow stay mostly preserved.
I was wrong!!! I could just open Krita and checked.
It already has these shortcut implemented in Krita, just need to configure. No need for external plugin or scripts.
Cheers.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
