Thanks again for the clear report and sorry for the unexpected behavior.
There’s certainly room for improvement, but this is actually how I expect it should work right now. (also for me undo seems to work fine in this situation, please let me know if you are sure there’s an undo bug). But maybe we can find a better way for a future release.
I think there are two absolute approaches to editing in a view with hidden gaps:
TaskPaper 2’s approach was that only visible items are affected. This seems reasonable (why I started with it I guess) … but is actually problematic. The problem is when you delete a project Because even when you delete a project it’s hidden tasks are left orphaned in place.
TaskPaper 3’s approach is to work like a programmer’s text editor (sublime or something similar). All text (hidden or not) enclosed by the selection is selected. This model seems simplest, and works well enought in those editors, but they have more visible fold indicators, and I think there folds are all hierarchical… so they don’t deal with filtered sibling items.
I guess there is a third hybrid option. Something along the lines of:
- Work like TaskPaper 3 if a visible ancestor is selected.
- Work like TaskPaper 2 if no visible ancestor is selected.
Anyway… I guess I’d like hear what you and other’s think. I know I don’t want TaskPaper 2 model. I think maybe with better indicators TaskPaper 3’s current model could work… though this hybrid model at the moment seems pretty nice.
Thoughts? How should it work!