allow_index_change not saved

Found a bug in "Everything"? report it here
Post Reply
w64bit
Posts: 58
Joined: Wed Jan 09, 2013 9:06 am

allow_index_change not saved

Post by w64bit » Fri Apr 20, 2018 2:17 pm

If I add "allow_index_change=0" in 901 ini file, at the next restart the line is deleted.

therube
Posts: 2290
Joined: Thu Sep 03, 2009 6:48 pm

Re: allow_index_change not saved

Post by therube » Fri Apr 20, 2018 7:12 pm

Confirmed.

stef
Posts: 1
Joined: Sun Mar 12, 2017 2:25 am

Re: allow_index_change not saved

Post by stef » Fri Apr 20, 2018 7:47 pm

It must be added to the Everything.ini located in the "Program Files"-directory (for example: c:\Program Files\Everything\Everything.ini)

void
Site Admin
Posts: 4819
Joined: Fri Oct 16, 2009 11:31 pm

Re: allow_index_change not saved

Post by void » Fri Apr 20, 2018 9:20 pm

allow_index_change is an admin only setting.

allow_index_change will only work when specified in Everything.ini in the same location as your Everything.exe.

allow_index_change makes the assumption that settings and data are stored in %APPDATA%\Everything and Everything is run as a standard user.

NotNull
Posts: 1364
Joined: Wed May 24, 2017 9:22 pm

Re: allow_index_change not saved

Post by NotNull » Fri Apr 20, 2018 9:28 pm

What does this option do? Is it comparable with the -read-only command-line option?

NotNull
Posts: 1364
Joined: Wed May 24, 2017 9:22 pm

Re: allow_index_change not saved

Post by NotNull » Sun Apr 22, 2018 10:02 pm

NotNull wrote:What does this option do? Is it comparable with the -read-only command-line option?
OK, found it:
Added allow_index_change ini option to prevent user from changing settings under Indexes.
(it's not in the regular help)


Suggestion for another way to "solve" this:

2 new entries for the 'central' Everything.ini:
Mandatory=drive:\path\inifile
Default=drive:\path\different_inifile


Where Mandatory references the settings that users can't change and ..
Default references the preset settings that users get when they start Everything for the first time (and thus don't have yet their personal Everything.ini

If there are no Mandatory= and/or Default= entries and a Mandatory.ini and/or default.ini exist in the program directory, those will be used.
When (re-) loading settings, load user-settings, followed by mandatory settings in RAM (=mandatory overrules user).

That way uou get a more simple, universal approach.
And no longer a need to deploy INI's to the users ..

It might be useful to have an option to show what ini's are used, as there can now be 4 different ones, all working together ...

Post Reply