You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, great extension you've created!
I'm trying to get export to work where it automatically creates additional columns for sub-tasks:
Basically, I think that the "part 1" and "part 2", as sub-tasks underneath "thing 4", should have their own empty csv column, and start being listed in the second column. You'd have to have a variable number of columns before the "start" and "end" time columns, in order to represent sub-task levels in this way. But I think it would be better / more intuitive.
Also, I tried coding up a solution that would simply detect the blank spaces in the timestamps, to auto-indent the stuff below. But in fact, it's not possible to do this, because there's no way to recognize when we've hit the last item in a sub-hierarchy! Eg. After Part 1, the task "Thing 5" is not recognizable as its own top-level task. This means no program analyzing it (or really, any person who didn't know about the tasks) would be able to recognize where a sub-task list ends and a new top-level task begins, as far as I can tell.
The text was updated successfully, but these errors were encountered:
Hi, great extension you've created!
I'm trying to get export to work where it automatically creates additional columns for sub-tasks:
Basically, I think that the "part 1" and "part 2", as sub-tasks underneath "thing 4", should have their own empty csv column, and start being listed in the second column. You'd have to have a variable number of columns before the "start" and "end" time columns, in order to represent sub-task levels in this way. But I think it would be better / more intuitive.
Also, I tried coding up a solution that would simply detect the blank spaces in the timestamps, to auto-indent the stuff below. But in fact, it's not possible to do this, because there's no way to recognize when we've hit the last item in a sub-hierarchy! Eg. After Part 1, the task "Thing 5" is not recognizable as its own top-level task. This means no program analyzing it (or really, any person who didn't know about the tasks) would be able to recognize where a sub-task list ends and a new top-level task begins, as far as I can tell.
The text was updated successfully, but these errors were encountered: