[Solved] allow_index_change not saved
[Solved] allow_index_change not saved
If I add "allow_index_change=0" in 901 ini file, at the next restart the line is deleted.
Last edited by w64bit on Fri Jan 21, 2022 3:33 pm, edited 1 time in total.
Re: allow_index_change not saved
Confirmed.
Re: allow_index_change not saved
It must be added to the Everything.ini located in the "Program Files"-directory (for example: c:\Program Files\Everything\Everything.ini)
Re: allow_index_change not saved
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.
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.
Re: allow_index_change not saved
What does this option do? Is it comparable with the -read-only command-line option?
Re: allow_index_change not saved
OK, found it:NotNull wrote:What does this option do? Is it comparable with the -read-only command-line option?
(it's not in the regular help)Added allow_index_change ini option to prevent user from changing settings under Indexes.
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 ...