-
Improvement
-
Resolution: Unresolved
-
Normal
-
None
-
2.5.2
-
None
-
Debian Linux, Buster (stable)
I've noticed that sometimes Picard does not see see filesystem updates that occur outside of Picard. I'm assuming this is from the filesystem change monitoring either missing some update notifications, or just that not working on certain filesystems due to missing support. That is not the issue at hand.
The issue is that once Picard has missed some filesystem changes for whatever reason, there doesn't seem to be any way (short of restarting Picard) to get it to update the file listings. Even clicking on now non-existent files/dirs and trying to do operations on them doesn't cause it to realize they aren't there anymore or that new files have appeared in them.
I think there needs to be an option in the file browser pane context menu to "Refresh" (selected dirs/files) and "Refresh All" (all expanded dirs/files). In addition, it would be good if picard re-scanned any directory that is actively being worked in within picard whenever a new operation is initiated in that directory (select, expand/collapse, scan, process, save, etc).
- is related to
-
PICARD-2098 The file browser (left pane) loses position if the currently highlighted folder is removed
-
- Open
-
-
PICARD-2152 Generated AcoustID is not shown
-
- Closed
-
I don't think having the display refresh/change is that big of an issue. Since the "refresh" action could be made so it will only be initiated manually, I would consider it almost expected to have the display refresh then too. Maybe most people never need it, and so it will never affect them. And given what you've said about it, my preference would be to have it re-center the selected item if that's the easiest. But if you are concerned about that, call it "reinitialize file display" or something instead of "refresh", as that makes it clearer that some state may be lost.
I would also point out that because the horizontal position already automatically re-positions whenever you select an item on a different level, having the vertical position re-center is also not unexpected, especially if it only occurs due to either a manually initiated process, or due to something detecting a verifiably inconsistent state (like a file operation/access failing due to it not existing).