Saving search results

[aimy]

I know I can save a search to a tab. Any time I want to re-run the search, I can select the tab. (Of course, I can also create a search template to re-run the search, too.)

Is there a way to save the found files from a search on a tab without re-running the search every time I click the tab? Can I just save results, not the search process? Thanks.

I've been reading all the post but I still fail to see the solution of this..

Can someone please guide me a clear step on how do I prevent XYPlorer from REPEAT THE SEARCH PROCESS everytime I switch the tab?? It is really annoying..

[admin]

Can someone please guide me a clear step on how do I prevent XYPlorer from REPEAT THE SEARCH PROCESS everytime I switch the tab?? It is really annoying..

See the advantage: you are being served fresh data always!

You can already save search results to the catalog via catalog ctx menu "Import As New Category.../ Current List". Not exactly what you want probably... but that you will get once I add Drop Stacks aka Virtual Folders!

[lukescammell]

I would personally rather have the search tab not save as well. If I want to be served fresh data I'll just hit F5 - this is expected behaviour after all. If nothing else this should be an option.

[j_c_hallgren]

I've sometimes clicked by error on the SR tab and then had to either wait for it to finish or ESC out, so having it auto-refresh can be a real pain on occasion...I can understand, however, that without a re-scan, there may not be the data needed for the list so: IF there was some way to easily temporarily cache the results, (somewhat like thumbs are?) then the tab could recover the list data from that...and redisplay without delay.

I wouldn't really need to save results for a long while...just enough (for example) so I could bounce to another tab, do something else, and come back to my prior results of search...and then use F5 to update it as desired.

If this cache of SR were emptied automatically when SR tab is closed or XY is exited, that'd be fine with me also...just so it holds results until next search pass...and this would need to be user option as well.

[jacky]

Relax guys, when Drop Stacks will be added other things such as cached SR will "come along", you just have to wait...

In the mean time, you'll have to hit ESC/use Stop button if you activated to the wrong tab, and only deal with live results.
As of today XY as no caching system of any kind, and there really is no reason to create one for SR now, when we know DS will come and allow this (among other things)

[j_c_hallgren]

My only reason for suggesting cache of SR was that (as I understood it) Drop Stacks would be for saving things more permanently rather than just until next function done...and I wouldn't desire to have to choose which DS to use to hold result unless I wanted to...but since exactly how DS will function still is unknown to me, so just wanted to bring it up.

[jacky]

My only reason for suggesting cache of SR was that (as I understood it) Drop Stacks would be for saving things more permanently rather than just until next function done...and I wouldn't desire to have to choose which DS to use to hold result unless I wanted to...but since exactly how DS will function still is unknown to me, so just wanted to bring it up.

Well how DS will (exactly) work is quite unknown to me too, but what I meant was, today XY has no caching feature of any kind (regarding what we're dealing with here), but once DS will be there, it will have one (DS!).

So then it should be pretty easy to have XY sometimes uses "internal" DS to do some things. For example, custom order, run a search within search results or, of course, cache search results.
I said "internal" as in XY would create a (temporary) DS and use it on its own, you (user) would not have to choose or do anything there. That's why i said we should wait for DS to get those features, since (as I see things) they would be pretty easy to implement, as every thing would be doable already using DS, "all" it would require is to have XY automatically use some DS without user interaction, but the core part (store & work on those stored file lists) wil already be done.