what's the difference between "pause updates" and "stop updating" in index menu

[tiddu]

title

[therube]

(Not that I knew before I looked, but) when you hover the different options, some help is provided on the (Everything) statusbar.

1 continues to monitor, but only updates when un-paused
the other, actually stops monitoring (so updates may be missed)

[defza]

Maybe it should be called "stop monitoring (ignore changes)"?
and "Pause index updates (keep monitoring)"

[ChrisGreaves]

Maybe it should be called "stop monitoring (ignore changes)"?
and "Pause index updates (keep monitoring)"

Hi defza. I have just caught this topic.
It still is counterintuitive to me.
As an exercise I created a file "eraseme.doc" and showed it in the Result List, then played around with "Pause Updates" while I modified the file, then in Windows Explorer renamed the file to "eraseme2.doc".

Thus emboldened (i.e. I thought I knew what I was doing!) I ventured into Stop Updates and recklessly used Windows Explorer to delete the file.
With "Update Indexes" turned back on, my result List remained unchanged.

(1) I can dream up a reason for wanting to inhibit changes in the result List, but those reasons don't sound valid, even to me.
(2) No matter how i play around with the "Update Indexes, Pause Updates, Stop Updating" settings, I really expected Everything to get back up to speed a minute or two after returning to "Update indexes" status.

Right now, it seems to me that switching between "Stop Updating" and "Update Indexes" might be useful if one wanted to insert a secret document "password.doc", but then (menu) Index, Rescan, Rescan All brings the index and the Result List back into line, revealing my secret passwords document.

@ALL I'd appreciate a rational reason for having these three menu items in place. I am sure that there is a rational reason, probably based on an enhancement request years ago?

In the meantime I have established some example/exercises at www.chrisgreaves.com/Downloads/MenuSystem.doc for anyone who would like to follow my path.
Cheers, Chris

[NotNull]

@ALL I'd appreciate a rational reason for having these three menu items in place. I am sure that there is a rational reason, probably based on an enhancement request years ago?

In version 1.4 one needed to wait before updates were processed before 'business as usual' could continue. To be able to temporary block upcoming Folder update schedules was very welcome new feature.
Now this is less of a factor as In Everything 1.5 updates are now processed in the background.

It is useful when looking at new/changed files. For example if you want to follow what files a program's installer adds/changes.
Stopping/pausing index updates at the right time will prevent other file updates to clutter the result list when sorted by date and keep the desired files in view.


Personally, I use it most when starting debugging (menu:Tools > Debug). Stopping indexing keeps the console/log 'clean'

[ChrisGreaves]

Now this is less of a factor as In Everything 1.5 updates are now processed in the background.

Thanks NotNull.
I recall seeing a post about this back sometime in the past couple of months. Immediate control over updating indexes across the system, rather than inhibiting updates on each device (in Tools, Options, Indexes) would make sense.

It is useful when looking at new/changed files. For example if you want to follow what files a program's installer adds/changes.
Stopping/pausing index updates at the right time will prevent other file updates to clutter the result list when sorted by date and keep the desired files in view.

I shall think about this.
Generally I just create a restore point and either restore the system, or use Revouninstaller to rid myself. I have little interest in scouring out every byte of data; getting rid of 99% is close enough for government work(grin)

I might give Stop/pause a try next time I install an application.

Personally, I use it most when starting debugging (menu:Tools > Debug). Stopping indexing keeps the console/log 'clean'

I wouldn't dare tamper with a debug log if one were requested. I always expect that the developer can locate the important stuff, and deleting or suppressing material in a log file that I don't understand is a bit like removing part of a cable or pipe underneath the automobile.
Thanks, Chris

[NotNull]

shall think about this.
Generally I just create a restore point and either restore the system, or use Revouninstaller to rid myself. I have little interest in scouring out every byte of data; getting rid of 99% is close enough for government work(grin)

To clarify: some people want to trace what an installer is up to; where it puts all it's files.
That is easy with Everything: sort results by date and all new files are on top of the resultlist, ready to be inspected.

... Until Windows start doing updates, your browser writes lots of file to disk, etc. Now these installer files are a moving target or even getting out of sight.
Stopping/pausing indexing can help here. It will basically temporary freeze the resultlist in time.

[ChrisGreaves]

That is easy with Everything: sort results by date and all new files are on top of the resultlist, ready to be inspected.
... Until Windows start doing updates, your browser writes lots of file to disk, etc. Now these installer files are a moving target or even getting out of sight.
Stopping/pausing indexing can help here. It will basically temporary freeze the resultlist in time.

Thanks Not Null. This week I have to teach Quickbooks which means i have to install it and learn it.

I understand the advantage of shielding the Result List from changes to irrelevant files.
But how exactly do the installation files freeze? It seems to me that during the process of installation, Windows will update visible log files and other files which exist outside the installed application.
Seeing that a new application has installed a DLL in the Windows folders is useful.

Too, I am not completely certain of the difference between Pausing and Stopping.

Using my Quickbooks installation as an example, does the following sequence sound correct (this is a non-critical application, so nothing important hangs on my doing this):-
(1) Create a Windows Restore Point
(2) In Everything: Index, Pause Updates – or Stop Updates? Which?
(3) Install the new application
(4) In Everything: empty the Search Box (to show “all objects”) and sort by date, descending.

If I have understood the process, this should deliver new files brought about by installing the application, but not the apparently endless confusion arising from the apparently endless and continuous updating of Windows files by Windows itself.
Thanks, Chris