Community
Participate
Working Groups
as the title says it it is pretty annoying when you need to rename several files.
right now we just refresh the tree, but we could use the same expansion storing we do for reload.
fixed. I had forgotten how bad this was. If you had something like: Folder1 Folder2 Folder3 Folder4 Then renaming any of these folders would collapse all the way up to Folder1. The original problem was that the tree refreshed the entire root. It was a lazy work around for the fact that expansions are cached by name, so the remembered expansions don't work, and you can't look up a renamed item in the treetable (since the row id's are based on the item name). So the fix is to refresh using the item's parent so that the child items (including the renamed items) will be updated and thus findable in the tree. We also remember the expand state of the renamed item if it is a folder, so that we can expand it once we've refreshed its parent and siblings. So...now you can rename Folder4, Folder3 and the state will remain. Note that we don't recurse/remember the expansion state any deeper than one level. So if you rename Folder 2 you end up with Folder1 Folder2 Folder3 Much improved...possibly some context if there were lots of children expanded could be lost, but never again do you lose the item that you actually renamed.
