Hi!
Hope all is well on your side, probably you are quite overloaded as some other people during pandemic.
Product success means more and more feature requests...
Tasks is a fantastic thing, but could be rounded a bit more. There are some other ideas, perhaps mine overlap some of those.
I would love to be able to clone tasks, change remote attached to a task, and such a bunch of things.
Besides, tasks become linked to a given config file, and it becomes a issue if you change configs. So, including the pointer to the related config file would be also quite useful.
Finally, I am unsure which is the design reason for having the tasks encoded in a binary, but that reduces portability and does not allow to reuse tasks contents. Perhaps an xml structure or a kind of json would be more palatable... even a flat config similar to rclone one...
Thanks in advance,
CT
ah, window resizing would be very useful. I use 150% scale in the screen for sight reasons and those big windows of tasks do not fit in the screen...
Hi! Hope all is well on your side, probably you are quite overloaded as some other people during pandemic. Product success means more and more feature requests...
Tasks is a fantastic thing, but could be rounded a bit more. There are some other ideas, perhaps mine overlap some of those.
I would love to be able to clone tasks, change remote attached to a task, and such a bunch of things. Besides, tasks become linked to a given config file, and it becomes a issue if you change configs. So, including the pointer to the related config file would be also quite useful.
Finally, I am unsure which is the design reason for having the tasks encoded in a binary, but that reduces portability and does not allow to reuse tasks contents. Perhaps an xml structure or a kind of json would be more palatable... even a flat config similar to rclone one...
Thanks in advance, CT ah, window resizing would be very useful. I use 150% scale in the screen for sight reasons and those big windows of tasks do not fit in the screen...