The tree (branch expansion) state of each window is independent. Each has the tree expanded to a different point, or has different branches expanded. When using Windows Explorer, I have many windows open. Only explicit caching will change this for search results tabs: the contents are then written to a file when the tab is backgrounded (or when the app is closed) and read again when the tab is foregrounded (or the app is opened).I love XYplorer the reason I can't use it instead of Windows Explorer is a limitation in tree and search handling which kills me, because I'd love to use it for everything. So when a tab is backgrounded its contents are completely gone. Firefox - the difference in approach is visible form the memory consumption. Yes, sorry, as a relative new user you cannot know this: In XY the tabs are not objects but only pseudo-objects (contrary to e.g. Not to distract from the main point though, this was a side-thought. Maybe it would be useful for me to understand a bit about how search results (or list contents generally) are handled in memory/disk with caching on and off, before anything more on this On reflecting about it, I'm not an expert in how XYplorer does its caching and data management (a) when the user does a search and then (b) views a different tab. Are you really saying that the cache should be on when caching is turned off? Stilez wrote:Also on the subject of search with caching off XYplorer recalculates the entire search every time you switch between tabs. Not every time the user just flips between tabs (without doing anything else). Surely this is not necessary? Once a search is calculated and its results displayed, then it is enough to update the search when the filing system notifies a change to the location folders, and only to recalculate the search "from the start" when the user actually requests (F5 or choosing "find now"). If tree state is independent per tab, then search location in one tab should be unaffected by changes to browsed locations in other tabs (even if auto-sync is enabled)Īlso on the subject of search with caching off XYplorer recalculates the entire search every time you switch between tabs.This is for full tree or whatever else is in the navigation pane, that its state can be set to be independent per tab Config option please to maintain tree state (ie what nodes are expanded/collapsed/selected) independently per tab.Ouch, I thought I had set that one years ago - and somehow it had been removed as an option! The remainder are valid: See config / find files / show search results in Stilez wrote:Also allowing multiple search results tabs would be nice Is possible ever since. If tree state is kept "per tab", then search results in one tab are not affected by tree navigation in another tab's tree.A larger (or unlimited) number of tabs can contain "search results".Config option to keep tree state "per tab".Please, can these be fixed or config options created to allow these behaviors? What I'd like in summary: It also means there is only the possibility of one search results tab at a time in XYplorer where Windows Explorer allows multiple searches open simultaneously. It also means when the tree or location changes in one tab, the linked search results changes in other tabs causing search results to be affected. It means if I expand or collapse branches in one tab those branches get expanded or collapsed for other tabs. In XYplorer the tree state is not "per tab" but global. So when I search, or navigate to a new branch, or change the tree state, in one Windows Explorer window, the other windows, search results etc that I might have open aren't affected (other than updates for list item changes such as deletion, copy, rename etc). I love XYplorer the reason I can't use it instead of Windows Explorer is a limitation in tree and search handling which kills me, because I'd love to use it for everything.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |