Session Restore tabs may not necessary display "correct" data

Discussion related to "Everything" 1.5 Alpha.
Post Reply
therube
Posts: 4952
Joined: Thu Sep 03, 2009 6:48 pm

Session Restore tabs may not necessary display "correct" data

Post by therube »

Session Restore tabs may not necessary display "correct" data.
I suppose that's what the deal is.

Some queries, or actions, do not, are not expected to update/refresh a display list.

So depending on your search (& other factors), results may not be accurate, & may require a Refresh to be so.


just noting...

on Session Restore
(i believe, but not certain that's [only] where it occurs)
with:

search:
!/$recycle !/music/ !/music.x !/CORRUPT !/100, !offline:

+ a UNIQ (filter) --->
video: sort:name: distinct:


if you then,
Find Size Duplicates

(with the intention, in my case, of finding files that i've
renamed in 1 place, but not another [cause other drive was
offline at the time])

it will display... (some) non-UNIQ (filter) files,
i.e., it will display files that are the same name,
i.e., not distinct:

if you then Refresh the list
& then (again),
Find Size Duplicates

the list is then properly pruned to display only
distinct: file size dupes


(perhaps ? the above is expected, given how certain actions
are not to always update the filelist - even like, with
above, when i do rename to files to be the same name, so
therefore no longer meet the distinct: criteria, they do
no "drop off" the list [a good thing in this case]
- until you refresh the list or perform some other action

anyhow, i saw that occurring, a number of times now, so i
took the time to try to understand... & now that i do,
i'm good)


And I'm now thinking, that in particular case, it was exacerbated by bringing an offline drive online.
void
Developer
Posts: 16665
Joined: Fri Oct 16, 2009 11:31 pm

Re: Session Restore tabs may not necessary display "correct" data

Post by void »

I haven't been able to reproduce the issue.

New results that are created/modified will ignore your distinct: filter.
It's possible some items were added/modified after the initial session restore.


And I'm now thinking, that in particular case, it was exacerbated by bringing an offline drive online.
This would cause Everything to perform a requery.
The requery should refresh your distinct: results.
Post Reply