Implement Tasks, so a user can run custom stuff after an screenshot has been made
Is currently under heavy work. Much more I'd like to add.
This arc patch can be used if you're impatient or want to add / change something :)
VDG | |
Spectacle |
Implement Tasks, so a user can run custom stuff after an screenshot has been made
Is currently under heavy work. Much more I'd like to add.
This arc patch can be used if you're impatient or want to add / change something :)
Configure -> Tasks -> enable checkbox and set a path for a custom script or program
No Linters Available |
No Unit Test Coverage |
Buildable 15524 | |
Build 15542: arc lint + arc unit |
Hm, looks like I borked my branches..
Now it shows the diff from the last two patches :/
And still including more than it should..
Can someone help me out with this one?
I love the idea. However is it likely that the user will always want to run the same task on every screenshot? It feels more like this should be a list of tasks, and the user should be able to choose which one to run, optionally marking one as an overridable default task.
Thoughts?
ShareX has an interesting approach, where one can set up multiple tasks. And after capture a new window appears with a bunch of options. But whatever on sets, that will be run - always. So a user has to know that task(s) x, y, z, will be run after every screenshot. By default, this would be off and I'd assume that only power users would use this feature.
Yes, I agree that there should be more tasks available and I'd like to hear suggestions to what kind of preconfigured Tasks should be available. And, as mentioned above, default would be nothing.
First of all this feature sounds great!
I am just a bit confused about how we define "tasks" now:
In your current implementation it looks like they should be executed after the file gets saved.
And after capture a new window appears with a bunch of options
This seems like an action gets executed after the screenshot is taken.
It shouldn't be a big issue to make it either after the screenshot has been taken or after the image has been saved. An user could set that easily with a checkbox.
Sound good👍.
But I can't think of any predefined tasks, because there are quite a few ones implemented with the Tools and Export button.
But maybe a nice example script with KDialog.