https://bugs.kde.org/show_bug.cgi?id=429265
Rebecca Breu changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=429265
--- Comment #5 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/krita/-/merge_requests/600
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429265
Rebecca Breu changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
CC|
https://bugs.kde.org/show_bug.cgi?id=429265
--- Comment #4 from Tymond ---
Well, right now it's two restarts (import, restart, enable, restart), automatic
enabling will make it into one, so already an improvement :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429265
--- Comment #3 from Boudewijn Rempt ---
And a restart of Krita, I thought you wanted to have the plugin activated on
import, instead of just enabled.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429265
--- Comment #2 from Tymond ---
Nope, it just needs an entry in `kritarc`, just like Script Starter does. See
plugins/python/krita_script_starter/krita_script_starter.py, line 290.
The only issue would be to find the exact name of the plugin to enable, b
https://bugs.kde.org/show_bug.cgi?id=429265
Boudewijn Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
--- Comment #1 from Boudewij