Summary: | Task Sets docker doesn't record tool invocations done on the toolbox | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Takiro Ryo <takiro-kde> |
Component: | Dockers | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | halla |
Priority: | NOR | ||
Version First Reported In: | 5.1.5 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Takiro Ryo
2023-09-03 10:56:56 UTC
That's to be expected: the task docker records invocations of QActions, and pressing a button in the toolbox doesn't invoke the action. (In reply to Halla Rempt from comment #1) > That's to be expected: the task docker records invocations of QActions, and > pressing a button in the toolbox doesn't invoke the action. While that seems logical from the code point of view I think it is still unexpected behavior from the users point of view. Especially since other "clickable" actions appear in the Task Sets docker when invoked from the main menu, even something like opening Krita's about page. The usage of the docker is restricted to tools that have a shortcut by default if the user didn't have set shortcuts for all the tools. Honestly I don't even know what the use case for the Task Sets docker even is, but I would expect a docker like that to record actions it no matter how the action was invoked. I believe most users won't know about the difference in how tools are selected. I only noticed this when I was testing it while helping someone else and this struck me as kinda odd that some things you click on work and others not. The task set docker was created to record the activation of QAction objects. It was created in 2011... Yes, we've got a lot of legacy stuff in Krita. It simply cannot record anything else than QAction activation, and if that's too confusing, we probably should just delete it. |