refresh (PoC) #216
refresh (PoC) #216
Conversation
- it doesn't deal with sub-trees - for that it would need awareness of the method that integrates tree events. - selection handling isn't implemented, so the selection just disappears. - if the root to be refreshed still exists, it should probably keep it selected instead of removing it. - it seems useful to have some control over the scope of the refresh, and these are sketched with the `Refresh` enum.
|
This is as easy I as was hoping it is going to be for a simple "big-bang refresh". I will have a look what needs to be done to finish this. Next step after that is to implement incremental updates or at least show what part of the tree is currently being updated. |
I think it's closer to Maybe tweaks to this are possible though, it seems a bit odd even though I always liked it that folders are completely known once they popup (and it would be nice to have a choice as well, like an immediate mode).
Yes, that would be optimal, and is probably going to introduce quite some complexity, maybe more than it's worth. But we will see. |
|
fyi, I have found quite a lot of bugs while working on this change so it will take some time before this will be ready |
|
No worries, no need to rush, and thanks again for your incredible help with this and |
|
Done: #219 This PoC can be now closed imho. |
Please see the commit messages for additional context.
I won't work on this, but it should show it this can work in general,
and to my mind this is already is a successful PoC, but needs work to
deal with the details.
PS: It's also unclear how well this will work with the
globnavigation pane, but it's probably worth trying and maybe we are lucky. If not, ignoring these keys in the glob pane should do the trick.