Windows 10, 10.0.19044.1645 (64-bit)
when the underlying file system is active (disk head read-write activity), freecommander can decide to change the active explorer tree's display location to the file tab's root. as frequently happens, i may be trying to copy / move files with FC, or simply locating a file in a specific directory, and can be interrupted by the change in the explorer tree. this can cause files to be moved/copied/deleted to/from the wrong folder.
freecommander environment - multiple folder tabs locked, two trees (upper, lower) visible. scroll bars visible on both trees.
1 open folder with MANY subfolders
2 scroll to a deeper subfolder (make sure the scrollbar moves), and select that subfolder
3 start a dos batchfile that will make file system requests (copy/move files, for example)
4 back on freecommander, watch as the tree (eventually) returns to the tab's root
i cannot say for certain simple read events cause the problem, but i'm reasonably certain write events and (usually) changes in directory or (perhaps?) opening a new batchfile using CALL or START will cause FC to lose its place. it's as if FC was monitoring file activity (it should, by default), but each time another process's file activity registered (file copied, folder changed using batchfile), the FC tree's current location was lost in favour of the batch's location). if there is no activity happening outside FC, the problem does not happen. i only notice it because i do major automated backups daily that talk to multiple drives on multiple machines locally and over a network.
backup settings available on request. could probably also make a video displaying change, though that might be more "interesting"
