What is the overall point of the "Set Instance Name" option? It seems overkill for what it's worth. #623
-
|
I use Everything, and Everything Toolbar religiously. They are an essential bit of kit that I can't live without. However, once in a while when I have to reinstall things, I am forced to have to reference the documentation to know what to set the instance name to when I use Everything 1.5 Beta. In my opinion, why is it not just a radio selection, or a context menu option in lieu of having to set the instance name? The contact menu "Set Instance Name" should be replace with "What version of Everything do you use?" with submenu choices of "Everything 1.4" and "Everything 1.5 Beta". To me, this would be much simpler on the end user side, and would have the end user have to reference documentation each time it's setup with the Beta version. I'm not sure if there is extended use of "Set Instance Name", but at this time, I can't find any other use for it, other than to specify use of the beta. 🤷♂️ Am I missing something here? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Named instances is a feature of Everything: https://www.voidtools.com/support/everything/multiple_instances/#named_instances Supporting them was a feature request from a long time ago. Unfortunately, Everything 1.5 alpha requires setting a different instance name, which I agree can be a bit confusing during setup. That’s just one of the quirks of using an alpha version. I expect the stable release of Everything 1.5 will not require this change anymore, so an option to select the 1.5a instance might break something in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, I suppose that makes sense. Just to be clear, I wasn't complaining or nagging, I was just genuinely curious as to why it was a text input as opposed to an option select. Thank you for the feedback, this clears things up :) Much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I wasn't reading it like that! Maybe I should think about an easier way to configure 1.5a though. Auto-detecting it, if no 1.4 is found might be an option and wouldn't really break anything either. |
Beta Was this translation helpful? Give feedback.
-
Bad idea. |
Beta Was this translation helpful? Give feedback.
-
|
I was thinking if the configured instance isn't found, and there's another instance running with the name |
Beta Was this translation helpful? Give feedback.
-
This way it's ok. |
Beta Was this translation helpful? Give feedback.
Named instances is a feature of Everything: https://www.voidtools.com/support/everything/multiple_instances/#named_instances
Supporting them was a feature request from a long time ago.
Unfortunately, Everything 1.5 alpha requires setting a different instance name, which I agree can be a bit confusing during setup. That’s just one of the quirks of using an alpha version.
I expect the stable release of Everything 1.5 will not require this change anymore, so an option to select the 1.5a instance might break something in the future.