Everything (1.5a) 1.5.0.1282a (x64)
I tested
/preview_visible=0
/preview_visible=1
/preview_visible=!
It should work, if not at real time, at least after restart. It doesn't work.
btw, tested also set it via
Menu| Tools > Debug > Config
It works.
But I wondering:
1. If /preview_visible=1 needs a restart, why doesn't it display a dialog-box (like in Debug > Config) asking for restart?!
2. Why Debug > Config asks always for restart?!
I tested for example:
/alternate_row_color=1
alternate_row_color=1
It doesn't require a restart. So why Debug > Config displays a dialog-box asking for restart?!
/preview_visible
Re: /preview_visible
Thanks for your feedback Stamimail,
How would this work with multiple windows? I'm guessing you would only want the window where the command was issued to update.
Each window has a copy of this preview_visible setting.
When you close a window the main preview_visible setting is updated.
Use View -> Preview or Alt + P to toggle the preview window.
/preview_visible= will set the main config setting which will be overwritten when you close an Everything window.
If Everything detects an external change to your config and you choose to reload, Everything will avoid saving to your config and restart with your new changes.
Assume changing any ini setting with /<ini-setting>= requires a restart.
I will consider marking which ini settings require a restart, which are available and which will not work as they will be overwritten by closing a window.
Using the UI is the preferred method for change your config.
The /<ini-setting>= search command wasn't designed for general use.
It's like about:config in a webbrowser allowing fine control over some settings that are not in the UI.
Each window can have the preview pane shown or hidden.I tested
/preview_visible=0
/preview_visible=1
/preview_visible=!
It should work, if not at real time, at least after restart. It doesn't work.
How would this work with multiple windows? I'm guessing you would only want the window where the command was issued to update.
Each window has a copy of this preview_visible setting.
When you close a window the main preview_visible setting is updated.
Use View -> Preview or Alt + P to toggle the preview window.
/preview_visible= will set the main config setting which will be overwritten when you close an Everything window.
When Menu| Tools > Debug > Config is executed, your config is written to disk to ensure settings are up-to-date.btw, tested also set it via
Menu| Tools > Debug > Config
It works.
If Everything detects an external change to your config and you choose to reload, Everything will avoid saving to your config and restart with your new changes.
But I wondering:
1. If /preview_visible=1 needs a restart, why doesn't it display a dialog-box (like in Debug > Config) asking for restart?!
Assume changing any ini setting with /<ini-setting>= requires a restart.
I will consider marking which ini settings require a restart, which are available and which will not work as they will be overwritten by closing a window.
Using the UI is the preferred method for change your config.
The /<ini-setting>= search command wasn't designed for general use.
It's like about:config in a webbrowser allowing fine control over some settings that are not in the UI.
Everything doesn't examine each value, it just sees the date modified changed on your Everything.ini.2. Why Debug > Config asks always for restart?!
Re: /preview_visible
What's the problem. Add a new syntax like:Each window can have the preview pane shown or hidden.
How would this work with multiple windows? I'm guessing you would only want the window where the command was issued to update
/preview_visible=1 == write to only this window memory, to RAM. (without saving to INI file)
/+preview_visible=1 == write to storage, to INI file.
I think for a better experience it would be better to map the functions, what requires a restart and what is available in real time.
If it's a big work, leave it till you see it's really needed.
Re: /preview_visible
I will consider something like this./preview_visible=1 == write to only this window memory, to RAM. (without saving to INI file)
/+preview_visible=1 == write to storage, to INI file.
Thank you for the suggestion.